> Correct. The Linux architecture around a global of dependencies is, imho, bad and wrong. The thesis is it's good because you can deploy a security fix to libfoo.so just once for the whole system. However we now live in a world where you actually need to deploy the updated libfoo.so to all your various hierarchical Docker images. sad trombone
Only if you choose to use docker. As other people have pointed out most things on Linux can be deployed using a package manager.
> A light alternative to Docker is simply deploy your dependencies and not rely on a fragile, complicated global environment.
So like flatpak?
> I know my opinion is deeply unpopular. But I stand by it! Running a program should be as simple as downloading a zip, extracting, and running the executable. It's not hard!
How is that better than apt install? That (or equivalent on other distros) is how I install everything other than custom code on servers (that I git pull or similar).
Only if you choose to use docker. As other people have pointed out most things on Linux can be deployed using a package manager.
> A light alternative to Docker is simply deploy your dependencies and not rely on a fragile, complicated global environment.
So like flatpak?
> I know my opinion is deeply unpopular. But I stand by it! Running a program should be as simple as downloading a zip, extracting, and running the executable. It's not hard!
How is that better than apt install? That (or equivalent on other distros) is how I install everything other than custom code on servers (that I git pull or similar).