4 ms·

what's wrong with nodejs?

50CNT 11y ago
Because .js. I think the general argument is this. Javascript is a necessary evil, but serverside, it isn't. Please, let us use something saner, or at least give us the option to do so. Javascript seems to be spreading into areas javascript has no business of being in, ("node.js on microcontrollers? what?"), and that is a bit disconcerting. Granted, I'm fairly new to Javascript, but even the good stuff seems like piecing together sane abstractions from wonky components. It's the horror you'd feel if a nuclear reactor operator told you they get the components to go subcritical by grounding that bare wire next to their coffee cup. Does it work? Yes. Abusing function scope and closures to make variables private? Write a function that checks whether a variable is an array because typeof malfunctions? Does it work? Yes. But then, is it sensible engineering? And even if you've gotten good enough at javascript that the gotchas simply seem kinky to you, do you really need it in every other area of your life? I'm also be a little bit concerned that javascript will swallow everything else, and then the only way to program is to engage in a kinky whipfest, and whilst as a German I enjoy a good kinky whipfest, it's really something for after work.
- melted 11y ago
  It's not sensible if you're principled about your technology choices, but if you just want to whip something up quickly and all you have are "full stack" developers, Node gives them the ability to use just one language for everything, as well as a pretty high performance runtime. So the value is there, given those constraints, which may or may not apply to you.
  - 50CNT 11y ago
    It does make sense in that context, but even then it seems like a dangerous choice to make depending on your development culture, especially if it only pays the minimums on technical debt. Javascript seems like the payday loan of technical debt. I think the fear and distrust towards it stems from the perception that it is on its way to become the lingua franca of development, and the expense of other much more suitable programming languages. That seems like a terrible idea.

50CNT 11y ago

Because .js. I think the general argument is this. Javascript is a necessary evil, but serverside, it isn't. Please, let us use something saner, or at least give us the option to do so. Javascript seems to be spreading into areas javascript has no business of being in, ("node.js on microcontrollers? what?"), and that is a bit disconcerting. Granted, I'm fairly new to Javascript, but even the good stuff seems like piecing together sane abstractions from wonky components. It's the horror you'd feel if a nuclear reactor operator told you they get the components to go subcritical by grounding that bare wire next to their coffee cup. Does it work? Yes. Abusing function scope and closures to make variables private? Write a function that checks whether a variable is an array because typeof malfunctions? Does it work? Yes. But then, is it sensible engineering? And even if you've gotten good enough at javascript that the gotchas simply seem kinky to you, do you really need it in every other area of your life? I'm also be a little bit concerned that javascript will swallow everything else, and then the only way to program is to engage in a kinky whipfest, and whilst as a German I enjoy a good kinky whipfest, it's really something for after work.

melted 11y ago
It's not sensible if you're principled about your technology choices, but if you just want to whip something up quickly and all you have are "full stack" developers, Node gives them the ability to use just one language for everything, as well as a pretty high performance runtime. So the value is there, given those constraints, which may or may not apply to you.
- 50CNT 11y ago
  It does make sense in that context, but even then it seems like a dangerous choice to make depending on your development culture, especially if it only pays the minimums on technical debt. Javascript seems like the payday loan of technical debt. I think the fear and distrust towards it stems from the perception that it is on its way to become the lingua franca of development, and the expense of other much more suitable programming languages. That seems like a terrible idea.