4 ms·
Not knowing much about node.js, wouldn't the most logical step now to make a standard node.js library that implements the majority of the functions of those ~40
by a_bonobo 8y ago
Not knowing much about node.js, wouldn't the most logical step now to make a standard node.js library that implements the majority of the functions of those ~400 packages? Vetting one package is easier than vetting 400. I guess that's what Rails did in the very beginning, I keep on discovering in-built magic
- buboard 8y agoi think a bigger issue is that many people don't even write javascript, but another language that transpiles to it
- rpeden 8y agoNode does have a standard library. It's not massive, but there's a lot more available out of the box than is available in a browser. The tricky part is that lots is npm packages end up bundled into an app that runs in the browser. It's just a guess, but I'd guess that significantly more npm imports end up running in the browser than in Node. So even giving Node a standard library as extensive as Ruby's wouldn't help as much as one would hope.