Well some of the libraries out there are glue for C++ code. I think that is what he was inferring anyways.

I don't see how the argument is any different than saying you have to use a "different Python" for web development and client-server development.

It's a little bigger consideration in this case imo, because one of the big selling points is the ability to do "JS everywhere" and share code between the browser and server side of apps. Not that that's the only reason node.js exists, but it's a nice aspect that becomes harder if the server and browser sides diverge more.

Ah, if that's the case then I misread.

If the problem is the broken promise of writing code once than runs perfectly well on the server or in the browser then I guess I could see the frustration. Although, I'm not sure that's an entirely realistic expectation given the different roles you'd expect the server and client to fill.