3 ms·
Yes, I think I'd probably settle for solution number 2. I still don't understand how this is better than NPM, and how Deno solves the horrible dependency manag
by bgdam 6y ago
Yes, I think I'd probably settle for solution number 2.
I still don't understand how this is better than NPM, and how Deno solves the horrible dependency management of Node, but maybe if I actually build something with Deno I'll get some answers.
- mkolodny 6y agoFrom the post: > [With NPM] the mechanism for linking to external libraries is fundamentally centralized through the NPM repository, which is not inline with the ideals of the web.
- Rapzid 6y ago> which is not inline with the ideals of the web Subjective. > Centralized currency exchanges and arbitration is not in line with the ideals of the web! - Cryptocurrency Nek minute. Besides, let's get real here; they will just end up centralized on GitHub. How exactly is that situation much different than npm or any other language ecosystems library directory being mirror-able?
- afiori 6y agoThe centralization of git on Github is completely different in nature from the centralization of Node packages on npm. git does not require Github to be online to work, nor relies on Github existence for its functionality.
- Rapzid 6y agoI'm talking about the centralization of software packages(Go, Deno) on GitHub as it applies to dependency resolution.