As a self-hoster, I love docker. It’s been an amazing deployment tool.

Same. Now, it is complete shit on Windows, though supposedly it is better on W11, and that is a no go. However, on Mac, it is a dream. On Linux it is a dream. Pgadmin, postgres, mqtt, redis, all the arrs, qbittorrent, jellyfin, and whatever else I want to try and throw away if I don’t like it.

a clean and functional site

But the specs no longer call for a clean, functional site. Today’s “professional” web development specs call for user tracking, customized content per user per platform per locality the page is being served to. Then there’s the backend dashboard services showing the overlords user behavior patterns and how they change based on tweaks made to their ui, I wouldn’t be surprised if the algorithms auto-tune presentation to optimize behavior.

It’s all the extra requirements, all the extra engineering that needs to be added that is IMO ruining web applications. Sure, they have huge benefits, but I hate when the application is simple but the backend is so overly engineered that it takes a week to completely build a fully fleshed out application. You have to organize your components, add styled-components.js, make sure it’s compatible with mui.js, create test cases for each component, setup a DB and integrate it to hold all copy as well as any input from the customer, make sure that it’s accessible (this part I admit that it’s important), make sure your test cases always pass, setup routing tables, add analytics, add pixel campaign api, squash git conflicts, integrate some other weirdo apis that marketing and leadership pulled from some obscure service no one has ever heard off, debug some weird edge case error caused by a node dependency 3 levels down, present the finished website to leadership only to be destroyed and now you have to redo 75% of the site with leadership changes… rinse and repeat.

It’s a good thing I fucking love my job 🙃

Yeah, but why would I use it when much worse options exist

Maybe it’s time to go back to the good ol’ days

Ah thanks, I do have another question actually! So aside from speeding up builds by parallelizing different stages, so that

FROM alpine AS two
RUN sleep 5 && touch /a
FROM alpine AS one
RUN sleep 5 && touch /b
FROM alpine AS three
COPY --from=two /a /a
COPY --from=one /b /b

takes 5 iso 10 seconds, are there any other ways buildkit speeds up builds?

Race condition that only happens on the much faster production hardware: Allow me to introduce myself

Unit tests? No matter where you run them, and normally this is done by CI in a prebuilt container image, so you don’t have to wait for “docker building”. Acceptance tests must be run in an environment as close to production as possible, but that’s definitely not a programmer’s job.

Yeah, and it’s useful to just check everything so you don’t forget to add some essential system package for e.g. SSL, especially when working with Alpine.

I mean, isn’t that kind of the point of containers? To basically have the same environment everywhere.