3 ms·
There's one primary tool¹ to access these "package registries" (repositories) though, and it's a 1:n relationship with the tool being generally able to use more
by eqvinox 3y ago
There's one primary tool¹ to access these "package registries" (repositories) though, and it's a 1:n relationship with the tool being generally able to use more than one repository. JavaScript seems to be doing n:1 instead with a whole bunch of frontends to npm.js? And the "special" thing about JSR is that it additionally(?) has its own repo?
Put differently — the tool is the standard, and you have a choice of repos. In JS it's the other way around?
I would describe the JS situation as… hmm… "oddly tilted" in comparison to other ecosystems; the closest thing I can think of is Python's package management situation?
[¹] I'm not counting GUI frontends here, since I'm relatively sure they just call into the same tool.
- chrisweekly 3y ago> "relatively sure" Sorry, but you're flat-out incorrect. See e.g. https://pnpm.io/motivation https://pnpm.io/motivation See also my response to your earlier comment; in the npm ecosystem you can choose your package registry, and your package manager/client, not to mention your target runtime. Coupling any of these distinct concepts is not the norm.
- eqvinox 3y ago> Sorry, but you're flat-out incorrect. I was talking about the non-JS world, i.e. tools like aptitude and Ubuntu's GUI package manager.
- Macha 3y agoapt-get, the modern apt command, aptitude... yum, dnf... The package registries also have multiple. Sticking with apt repos, Ubuntu has one per release, Debian has one per release, Mint has one per release... So it's an n:n situation.