The underlying problem is the kool aid drinking, not node.js
node.js is neat but it's also immature and incomplete. There are all types of "applications" were it would be a good choice or at least worth consideration. But if you pick it (because you know javascript and don't wanna learn Erlang) over say Erlang/OTP for serious a/o large production deployment you're probably and idiot and certainly a "too much kool aid drinker."
Of course some things do make it easier - frameworks, libraries etc. But they often only make it easier at the start before your project gets complex and needs custom out of the box things.
Programmers should just knuckle down and try to improve their skills rather than chasing the latest fads.
His main gripe here is that the server's javascript and the browsers' javascript isn't 100% the same, and that current libraries don't run on both.
Jeez, give it some time. Or better yet, work on it.