Isn't this just kicking the can down the road though? The incompatibilities are still something you either have to deal with or users end up with 58 outdated versions of each library and the security vulnerabilities they bring.
> Once you've started using language package managers, it become very apparent that they have huge value, that apt-get doesn't bring.
This is what's wrong with so much modern development, we do what's easy for developers, not what's best for users.
In the client software case, software that works is what's best for users. If you upgrade a library and apps start working, that sucks.
If you're running server-side software, you want dev-production parity, or you can't know it works. So you _need_ to use a package manager. But the same applies to client software: you can't test all these permutations, so you can't even tell it works, and it probably doesn't.
If you're running server side you should have test environments that match prod to be able to catch incompatibilities early.
In particular, you get the exact version of the library you want. If you've ever had the experience of trying to make your software work with multiple versions of its dependencies because different OSes ship with different versions, then you'll know how annoying this is.
This is particularly true of run-time problems. If they don't compile, then that's relatively easy to fix. If there's a difference at run-time, its often way more expensive to fix.
With a package manager, you get the exact version, but you also can use different versions for different apps on your system. You can also upgrade without breaking other apps (new security version) or not upgrade if there's some good reason not to.