Earlier quoted context omitted.
I like to use NodeJS too, JavaScript is a great misunderstood language that will handle the vast majority of use cases in the world of CRUD. Honestly, there is something to be said for hacking something together quickly. Prototyping is a great way to explore ideas and find the interesting problems nested in the problem you're trying to solve. I just don't like the evangelism of Meteor because I've never seen anything…
Sure it will handle CRUD just fine, like PHP did for all those years, but thats a low standard to measure yourself against. ECMAScript 6 does look kinda decent, but thats the future, not the present. Also, why use it (Node.js) on the server? Its not even that fast, 21th on the techempower Json benchmark, which should be its strongest discipline (all I/O, no computation, emitting Json).
Not only it's still reasonably fast (21st is great, it's mostly surpassed only by C and Java), but it also has a much better ecosystem than most platforms (especially C and Java), it's faster to develop in (especially C and Java) and shares language with client side.
Sharing a common codebase is very important for me. I found in most of my web projects I'm reusing code between server and client. Ever worked with code that does (or should do) the same thing in different codebases? It's just a nightmare.
Having the same React code be rendered in the server (fast, SEO-friendly) and in the client (offloads resources off the server) is just too good.
NodeJS looks like a decent compromise to me, isn't it?