4 ms·

Good reason to use Nodejs: The community. The amount of innovation, available toolset and the pace that everything moves forward (while keeping backward compat

Good reason to use Nodejs: The community. The amount of innovation, available toolset and the pace that everything moves forward (while keeping backward compatibility) is incredible. And now async/await is available and there are proposals for static typing in next version. That's the good thing about this community that I love. The community identifies a problem and within a couple of years its fixed. callbacks suck? Promises, Generators and now Async/Await are there which essentially solve the issue. (And the community has embraced them all already) There are proposals for optional static typing for next version. I think once the static typing is there, there arent many reasons not to use nodejs.

eeZah7Ux 9y ago
None of the things you mentioned were invented by the nodejs community. Reimplementing existing ideas is hardly innovation.
- topbanana 9y ago
  The point being made is that the problems are solved
- 0x7037 9y ago
  Old/new ideas reimplemented in a way that provides more value are, indeed, innovation. You're confusing with "invention". You might think: "oh well, vocabulary". But that's precisely this difference that matters.
throwaway47861 9y ago
- 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.

eeZah7Ux 9y ago

None of the things you mentioned were invented by the nodejs community. Reimplementing existing ideas is hardly innovation.

topbanana 9y ago
The point being made is that the problems are solved
0x7037 9y ago
Old/new ideas reimplemented in a way that provides more value are, indeed, innovation. You're confusing with "invention". You might think: "oh well, vocabulary". But that's precisely this difference that matters.

throwaway47861 9y ago

- 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.