3 ms·
There’s a pretty good reason, actually, and it’s exactly npm. Because dependencies are managed so easily in Node, it makes no sense for Node core developers to
by mumblerino 6y ago
There’s a pretty good reason, actually, and it’s exactly npm.
Because dependencies are managed so easily in Node, it makes no sense for Node core developers to implement more and more of the ever-expanding APIs offered by the browser. They’re better off spending that time tightening the system and perhaps offering low-level interfaces.
- throw_m239339 6y ago> There’s a pretty good reason, actually, and it’s exactly npm. You mean whoever created NPM the business profited from Node JS barebone standard library, which Node JS creator himself regretted creating an opportunity for a commercial package manager and registry by making his creating depend on such commercial product.
- dcgudeman 6y agoProfited? I thought NPM had to be acquired because they couldn’t figure out a sustainable business model.
- throw_m239339 6y ago> Profited? I thought NPM had to be acquired because they couldn’t figure out a sustainable business model. Since when acquisitions are free for the buyer? Someobody made a lot of money from NPM.