3 ms·
Maybe the JS language itself should vet and absorb some of these more common libraries. Printing pretty colors in a console could be a feature of the language i
by alana314 5y ago
Maybe the JS language itself should vet and absorb some of these more common libraries. Printing pretty colors in a console could be a feature of the language itself.
- CottonMcKnight 5y agoThere is a TC39 proposal for a "Javascript Standard Library." It's at stage 1, which is better than stage 0. https://github.com/tc39/proposal-built-in-modules https://github.com/tc39/proposal-built-in-modules Even so, unlikely that a "Faker" would become part of any such standard library.
- no_way 5y agoThere was a major push few years ago, but it died down. Basically performance benefits of built modules weren't worth it and with that standard library proposal also lost momentum.
- throw_m239339 5y ago> Maybe the JS language itself should vet and absorb some of these more common libraries. Printing pretty colors in a console could be a feature of the language itself. Maybe Node.js should start shipping with a substancial standard library instead of making developers rely on NPM. Node.js can't even parse a multi-part request body without a third party library. So much for a HTTP server that doesn't even implement the HTTP spec...
- o_m 5y agoIsn't Deno doing this with its own standard library?
- pawelmurias 5y agoA standard library over time would end up consisting of ancient garbage. You could have a vetted collection of node.js module on npm.
- soylentgraham 5y agoWhat if my engine doesn't have a pretty console? Javascript isn't just node and web browser scripting. Things like UI should not be in the language.