earlier replies
Replying to @ewolff
@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
@stilkov Which? BTW async I/O is also an option e.g. with #vertx
1
@ewolff Sure, but of course vert.x is a reaction to Node.
1
@stilkov ...and adds polyglott programming
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.
1
@stilkov My point exactly. And they are probably cheaper than Java guys...
2
Replying to @ewolff
@ewolff Cheaper? I find that hard to believe – especially if they know what they're doing :-)

Jun 25, 2013 · 8:22 PM UTC

1
Replying to @stilkov
@stilkov @ewolff +1 The real hardcore JS guys are pretty rare and just as expensive … at that's least my recruiting experience.
2
@devpg @stilkov @fmueller_bln Heard a story about a small pizza delivery using Node.js - I guess because some JS hackers did it cheaply.
1