@ewolff But you can use Node to build network clients just as well as servers. No need to restrict it.
2
@stilkov I guess my point was: people are like "Node.js = high scalability" while more important is "Node = JS on the server"
1
@ewolff I see. My view is it makes async/evented I/O a tolerable option for mere mortals; that's the more important point to me
1
@ewolff Sure, entirely awesome, not questioning that at all. Still, it was created because of Node's popularizing async :-)
1
@stilkov I would argue NodeJS would still be successful with sync I/O - even though that is probably really hard for JS guys.
1
@ewolff Interesting. My sales pitch on Node is that it's a portable, high-performance async I/O runtime with JS as its DSL
1
@stilkov It's the only choice JS guys have to develop a server I would argue.
2
@ewolff Yes, that's probably true. Would be interesting to find out how many JS folks started server programming because of Node.
Jun 25, 2013 · 8:21 PM UTC
1