3 ms·
I think the author's argument wasn't that JS was a 'productive' language but that it was an overall poorly designed and bad language.
by nickthemagicman 6y ago
I 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.