Hacker News new | ask | show | jobs
by mumblerino 2092 days 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.
1 comments
throw_m239339 2092 days 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.

link
dcgudeman 2092 days ago
Profited? I thought NPM had to be acquired because they couldn’t figure out a sustainable business model.
link
throw_m239339 2091 days 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.

link