Hacker News new | ask | show | jobs
by AnIdiotOnTheNet 2748 days ago
I don't know, I think the answer is pretty obvious: use system-wide shared libraries for things that are very common, like widget toolkits, network libs, cryptography, and other system components. Otherwise it is part of the application, not the system, and should be with the application.

The reason you don't see this on Linux is because there is no such thing as a separation between 'system' and 'application' in its culture. Consequently there has never been a "base system" to target or keep compatibility with so applications have to either target a specific version of a specific distro (waste of time) or include everything above the stable kernel ABI in their product (waste of space).

It is actually a very simple problem to solve, it just isn't one that the Linux community is interested in solving simply, so instead they invent ridiculously complicated tooling like package managers and Flatpak, introducing a bunch of unnecessary limitations and yet more parts to break and ruin your day.