NPM is both a massive repository as well as a package manager.
Deno will (soon?) have a package manager, but it won't be tied to one central repository run by a private company, now part of a massive corporation (Microsoft.)
So let's not lump package manager and repository: you can have a package manager that pulls in all the exact or latest dependencies at build time, but it does not have to be tied to one central repository owned and administered by one company.
It's not about choosing a different registry for all your modules, which will almost always be a commercial for-profit entity due to the cost of running and maintaining a centralized repository of that scale. AFAIK, or as far as I can envision, it's about a future where we can have the repository be a decentralized graph. It's definitely more challenging but we won't be dependent on one or few companies to host all modules. What do you think of that idea? My point is Ryan was right to avoid recreating dependence on commercial for-profit entities.
NPM is both a massive repository as well as a package manager.
Deno will (soon?) have a package manager, but it won't be tied to one central repository run by a private company, now part of a massive corporation (Microsoft.)
So let's not lump package manager and repository: you can have a package manager that pulls in all the exact or latest dependencies at build time, but it does not have to be tied to one central repository owned and administered by one company.
Centralize-able yet decentralized.