News for hackers. Stuff that matters.
Re:Yarn – A new package manager for JavaScript by mschuster91 on Tuesday October 11, 2016 @01:18PM (#12686380)
> That, to me, is what is wrong with npm. The problem stems from node.js not coming with "batteries included" so there is a proliferation of tiny libraries that do the most trivial things.

This is in no way a fault of node.js but of the whole JS standard. People these days use npm modules to run in a browser and ship stuff bundled together with webpack (or other bundlers), so even if nodejs had a proper stdlib, you'd still need to depend on a polyfill so that your stuff works in a browser environment, too.

And due to the fact that even if a sane stdlib would ever be standardized, it would take YEARS of time until it reaches significant market share (looking at you, Android, Safari and IE), so you'd always have to ship a polyfill.

Re:Yarn – A new package manager for JavaScript by lukeschlather on Tuesday October 11, 2016 @01:26PM (#12686468)
That's kind of a red herring when it comes to NodeJS. Webpack and the 50 other tools you need to run it are in a completely controlled environment. Most of the build tooling is working around issues with NodeJS, and NodeJS doesn't need to wait for anyone to come up with improved APIs around filesystem interactions and build tooling. This is purely build-time stuff.
Re:Yarn – A new package manager for JavaScript by jay_kyburz on Tuesday October 11, 2016 @06:39PM (#12689102)
Yeah, but we could have a big, standard library polyfill, and it would quickly find its way into everybody cache, just like jQuery.
Re:Yarn – A new package manager for JavaScript by toefraz on Tuesday October 11, 2016 @11:20PM (#12690229)
We do. It's called Lodash.