You think of distribution packaged rpms/deb, but the softwate developer can self publish, and you’ll see plenty of self published packages in ppa, copr, flathub, and even just loose websites because it’s not rocket science to make an apt or yum repository. However the distribution versions may take a little more time, but more likely to work together as a cooperative whole. Flathub has a decent shot by allowing concurrent versions of dependencies to install, while preserving the concept of updating dependencies independent of the package maintainers.
However, as you go down his chart, it’s less likely that you’ll reasonably update after install. You may get the latest at the second you install, but 6 months later you’ll likely be stale. You may neglect to update npm in each and every project, or it may automatically dependency lock (because self publish nature results in developers having to vet dependency updates, and devs are lazy about that).
And not have to wait for a maintainer to update the package to have the latest version.
You think of distribution packaged rpms/deb, but the softwate developer can self publish, and you’ll see plenty of self published packages in ppa, copr, flathub, and even just loose websites because it’s not rocket science to make an apt or yum repository. However the distribution versions may take a little more time, but more likely to work together as a cooperative whole. Flathub has a decent shot by allowing concurrent versions of dependencies to install, while preserving the concept of updating dependencies independent of the package maintainers.
However, as you go down his chart, it’s less likely that you’ll reasonably update after install. You may get the latest at the second you install, but 6 months later you’ll likely be stale. You may neglect to update npm in each and every project, or it may automatically dependency lock (because self publish nature results in developers having to vet dependency updates, and devs are lazy about that).