- Innovation: subjective. People can't even agree on an universally agreed upon definition. Still, care to give an example?
- Available toolset: oh, you mean the dozens of builders, packers, or task runners, being only three examples? Or the `leftpad` fiasco, maybe?
- async/await are syntactic sugar. They solve programmer happiness. Granted that's a big win (no sarcasm), but let's be clear on the semantics. That's not optimizing anything in a technical sense, it makes it more pleasant and quicker to write the code.
- "Within a couple years the problem is fixed". You should communicate with more business people. If I had to pick a technology today, based on what is available today, Node.JS wouldn't even make the top 10. By your logic, being optimistic for the future is a decision maker. That's actually not far off and sadly all of us devs make decisions based on such emotions, but IMO Node.JS shouldn't be judged on that basis.
- "Proposals for OPTIONAL static typing". Great, one more thing to track backwards compatibility on. Can't you see how the JS community is just happy to pile a hack on top of a hack, to infinity and beyond? It's surprising and saddening to me that this isn't obvious to so many JS devs.
---
Apologies, sir/madam, but you lack the bigger picture perspective. You like the stack? Nobody should criticize you over that, we all have fandoms. But you need to be more objective and identify the lingering problems. Shiny new proposals don't necessarily fix anything.
- Available toolset: oh, you mean the dozens of builders, packers, or task runners, being only three examples? Or the `leftpad` fiasco, maybe?
- async/await are syntactic sugar. They solve programmer happiness. Granted that's a big win (no sarcasm), but let's be clear on the semantics. That's not optimizing anything in a technical sense, it makes it more pleasant and quicker to write the code.
- "Within a couple years the problem is fixed". You should communicate with more business people. If I had to pick a technology today, based on what is available today, Node.JS wouldn't even make the top 10. By your logic, being optimistic for the future is a decision maker. That's actually not far off and sadly all of us devs make decisions based on such emotions, but IMO Node.JS shouldn't be judged on that basis.
- "Proposals for OPTIONAL static typing". Great, one more thing to track backwards compatibility on. Can't you see how the JS community is just happy to pile a hack on top of a hack, to infinity and beyond? It's surprising and saddening to me that this isn't obvious to so many JS devs.
--- Apologies, sir/madam, but you lack the bigger picture perspective. You like the stack? Nobody should criticize you over that, we all have fandoms. But you need to be more objective and identify the lingering problems. Shiny new proposals don't necessarily fix anything.