3 ms·

"An 'average weekend warrior' or people 'without programming experience' who are daunted by the complexity of Java should not be implementing server application

"An 'average weekend warrior' or people 'without programming experience' who are daunted by the complexity of Java should not be implementing server applications (see PSN security issues)" Disagree. If well-trained professional programmers were the only people implementing server applications, we wouldn't be where we are today. The fact that people can tinker, teach themselves, put together a highly-insecure server just to share their implementation with others provides a huge benefit to all programmers and the industry in general. Thus trolling. And again, "I don't understand why anyone would use node.js" is link bait trolling. Anyone means anyone. I bet if the OP really thought long and hard (or just for 10 seconds) he/she could come up with at least a reason one person would use node.js. Coming up with one person makes the OP's title a false statement.

3am 15y ago
You are coming up with a blanket judgement based on a small subset of a post (and in my opinion, not interpreting it as the poster intended). It read to me like he was talking about production usage, not tinkering. Node.js is slower and more resource intensive than Erlang (if you're comparing just async/message passing models), less productive for _most_ programmers than RoR or PHP, not as battle tested (security/stability) as Java, and fewer 3rd party libraries than most. I don't even know about the state of development tools like debuggers and profilers. My understanding is that Node.js still has stability issues (memory leaks or GC bugs?) and doesn't utilize multi-core machines very well, either. I'm all for tinkering, and I expect Node.js to be very successful and as an additional benefit to improve the V8 engine. But you're being overly sensitive to call this mild critique (albeit with a bad title) trolling.
- crcastle 15y ago
  Yeah, I agree that I got a bit worked up in my response and my language was a bit stronger than it needed to be. I guess it was driven a bit by: a) nodejs is resulting in a ton of interesting projects. whether it is the best design decision to use nodejs in these projects instead of something else is another question. the creativity nodejs has helped spark is awesome in itself. b) if the OP was referring to creating battle-tested server applications, he/she should have made that clearer. yes nodejs is immature and crashes left and right. c) OP titles like this one (i.e. generalized statement the OP knows to not be true) do not foster productive discourse and community

3am 15y ago

You are coming up with a blanket judgement based on a small subset of a post (and in my opinion, not interpreting it as the poster intended). It read to me like he was talking about production usage, not tinkering. Node.js is slower and more resource intensive than Erlang (if you're comparing just async/message passing models), less productive for _most_ programmers than RoR or PHP, not as battle tested (security/stability) as Java, and fewer 3rd party libraries than most. I don't even know about the state of development tools like debuggers and profilers. My understanding is that Node.js still has stability issues (memory leaks or GC bugs?) and doesn't utilize multi-core machines very well, either. I'm all for tinkering, and I expect Node.js to be very successful and as an additional benefit to improve the V8 engine. But you're being overly sensitive to call this mild critique (albeit with a bad title) trolling.

crcastle 15y ago
Yeah, I agree that I got a bit worked up in my response and my language was a bit stronger than it needed to be. I guess it was driven a bit by: a) nodejs is resulting in a ton of interesting projects. whether it is the best design decision to use nodejs in these projects instead of something else is another question. the creativity nodejs has helped spark is awesome in itself. b) if the OP was referring to creating battle-tested server applications, he/she should have made that clearer. yes nodejs is immature and crashes left and right. c) OP titles like this one (i.e. generalized statement the OP knows to not be true) do not foster productive discourse and community