4 ms·
Okay, how many node package managers do you think there are for the npm registry? Bower? Nope, it used github. Entropic? Nope, federated as an alternative to
by pluma 7y ago
Okay, how many node package managers do you think there are for the npm registry?
Bower? Nope, it used github.
Entropic? Nope, federated as an alternative to npm Inc's monopoly.
JSPM? Nope, it loads modules directly off the web.
Pnpm? Ah, yes, this one is actually a replacement for the npm client like yarn although with much less traction.
So we have npm, yarn and pnpm. Compare that to apt, aptitude, apt-get, dpkg, synaptic, gdpm, gnome-apt, dselect, wajig, PackageKit, kpackage and gdebi. Sure, most of these are GUI tools or somehow build on low-level tools like apt-get but the point is that "Linux doesn't suffer from fragmentation but JS package management does" is absurd.
EDIT: This doesn't even go into there being at least three popular mutually incompatible package systems for Linux (Arch/RedHat/Debian) and every distro having its own registry (or "repository").