The goal of an operating system is to run applications. The installation and packaging of software should be as simple as possible.
For whatever reason, the Linux desktop community does not see this as an issue.
If I want Vim 7.4, 7.3 and 7.1 installed at the sametime, your package manager should support it. What if 'X' plugin is only compatible with 7.1 and 'Y' plugin is only compatible with 7.4. This is a valid use case.
Lately, I have been using Docker to work around this, but it's not fun setting up GUI applications in a container.
I feel like your emphasis is backwards.
It's not surprising that NodeJS, a new project, has solved some of these problems. NPM has the luxury of decades of experience from dozens of linux package managers and package managers from other languages. Plus, they're not tied to the legacy use cases the same way that (e.g.) apt is.
Not supporting multiple versions of the same software is something that I identified as a problem though.
[0] - https://nixos.org/nix/
These requirements are not mutually exclusive. With a proper file system hierarchy both of them could be accomplished.
Most of the popular distribution's package managers (apt, pacman, etc) support the sharing dependencies but almost none of them support installing multiple versions of the package.
Given that storage space is very cheap nowadays I think a package manager like NPM which stores copies of the dependencies is not that bad actually.
However, the system should be designed in a manner where I have a choice.
This here: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
Makes no sense in a world of dynamically linked libraries and 6 month release cycles.
They do and they have, but they can't conjure-up libraries that haven't been properly versioned and released upstream.
If the GTK+ team can't maintain an ABI then they need to start releasing versions under different sonames such that programs like wireshark link against "libgtk-3.so.0.1200.2" and not "libgtk-3.so.0", then the package managers will be able to do the right thing.
Uh, they have. For ever.
I have parts of boost 1.49, 1.53, 1.54 and 1.55 together on my system. I have GTK2 and GTK3 together on my system. I have Qt3, Qt4 and Qt5 together on my system. Python2 and Python3. libpoppler19, libpoppler44 and libpoppler46.
If Linux/Linux distributions did support it, rolling release would be a lot more common. One limitation that would remain is that if you have an application that requires a single instance (e.g. a Network Manager), you couldn't have multiple instances of it running at the same time.