3 ms·
Javascript these days is a very productive language, especially with Typescript. Node however, with its lack of a remotely passable standard library, is not doi
by egeozcan 6y ago
Javascript these days is a very productive language, especially with Typescript. Node however, with its lack of a remotely passable standard library, is not doing it justice.
The async await is amazing and top level await works just fine in a browser console. The fact that node still has it behind a flag is... I mean, they surely have their reasons and I don't know enough to question the decisions of the maintainers, but it feels detached from modern times when using.
Node is not web, don't know why they hesitate so much before remotely breaking things. I'm not advocating for moving fast and breaking things, remind you, I'm just saying that the io.js kick maybe needs to happen again.
- nickthemagicman 6y agoI think the author's argument wasn't that JS was a 'productive' language but that it was an overall poorly designed and bad language.
- egeozcan 6y agoSo my argument is that a significant portion of the poorly designed part comes from node. It's also not a bad language. It's okay for its main purpose: Creating web applications. If people start using it to write distributed systems, async/await won't save you from any troubles you might have. Next.js is a perfect example for what JS is good for. However, the super lacking standard library frustrates me to no end.
- nickthemagicman 6y agoIt's not bad. Would I rather use anything else if possible? Yes.