News for hackers. Stuff that matters.
Re:AWS pre-announces public container image registry by indymike on Tuesday November 03, 2020 @07:17AM (#24978934)
Open source is a trade-off. In many cases, it's rocket fuel for early and mid-stage growth in exchange for reduced barriers to entry for competitors. It also points out a real weakness in infrastructure: why is provisioning, configuring and deploying code so difficult and expensive? Shouldn't we have OS level tools that make this trivial at this point? It's pretty amazing that we're taking patterns like load balancer + Shared Cache + Database + Libraries + App Code + config files and assets and making it so difficult to configure them and deploy them. Reducing deployment complexity is still a huge opportunity...
Re:AWS pre-announces public container image registry by donmcronald on Tuesday November 03, 2020 @08:16AM (#24979318)
> Reducing deployment complexity is still a huge opportunity...

I agree with that. There's probably even room for another CI system that's highly opinionated and focused on building images. Most of the existing ones kind of suck at building images.

Re:AWS pre-announces public container image registry by jonfw on Tuesday November 03, 2020 @09:18AM (#24979824)
We use Tekton where I work- which is really great in a K8s context.
Re:AWS pre-announces public container image registry by devthane on Tuesday November 03, 2020 @09:36AM (#24979967)
Agreed, we use it as well, it’s shaping up nicely, though its a good bit more user complicated than other solutions. But hey, this is Kubernetes.
Re:AWS pre-announces public container image registry by xnx on Tuesday November 03, 2020 @02:17PM (#24982930)
Deploying apps is truly ridiculously complex. This is the problem I really see "no code" addressing. To me, writing the logic of an application is easy compared to the ridiculousness of publishing the code somewhere.