Oh my. I like node, but that's a bunch of weird arguments. Most of them contain a kernel of truth, but jumping from that to node comes as some kind of non sequi

Oh my. I like node, but that's a bunch of weird arguments. Most of them contain a kernel of truth, but jumping from that to node comes as some kind of non sequitur. 1) Version hell: No up-to-date packages on Linux distributions? As compared to the packages they have for a fictional stable node version? 2) Rails 3: I thought you were talking about sinatra? Where did Rails come into this? 3) Again with the versions. It would be nice to give a good reason why for him the push to 1.9 would be so important. 4) Speed: Yes, the V8 engine is quite fast. This won't matter for most of your work, though. Most of the heavy lifting for Node's event system is done by libev (written in C), the same that's underneath Eventmachine. Compared to I/O, it will hardly matter. And if it will, then moving to a compiled or JVM language will probably still be better. 5) Mobile: What's wrong with JRuby? It's closer to Dalvik than anything else. And again, what's the connection to node? You're not much better of there, never mind that it uses the same engine as in the (Froyo) browser. 6) Familiar frameworks: Not that familiar, as event-driven code has to be a bit different. But yeah, you've got a sinatra clone... 7) Javascript: Finally a good point. A single implementation language is usally quite nice, and not everyone wants to go the Seaside/Parenscript route. Don't get me wrong, it might as well be a good decision, but these arguments are a bit immature, especially all the blabbing about Ruby 1.9, which isn't exactly the complete and utter miraculous revolutionary step.