3 ms·
Needing a container (outside of a system publishing reference builds) is evidense of a problem. The fact that a container is easy today just enables and hides
by Brian_K_White 5y ago
Needing a container (outside of a system publishing reference builds) is evidense of a problem.
The fact that a container is easy today just enables and hides the fact that it's a bit ridiculous to need one for half of the things we now use them for. Same for snap, flatpack, appimage, etc.
Rather than have a handle on my surface and interface with the os, I'll just bundle an os with my calculator app.
All because they're using a newer version of some library that maybe has an extra param on one function to automatically zero-pad or something.
And "they" isn't necessarily the developer of the calculator app but could be the developers of any of the hundreds of dependencies.
We all know all the excuses how we got here. We all know how each individual step along the way has it's excuse. Yet, it's not a great place we got to.