NodeJS's asynchronous approach is a concurrency (but not parallelism) approach. Your reference to "Pentiums" (which I assume is intended to be a reference to single-core nodes) suggests that your concern is actually with parallelism rather than concurrency.
But, sure, a not uncommon usage pattern for an IaaS like GCE might be to have lots of single-core nodes cooperating, rather than running individual processes on larger nodes with lots of parallel threads.
Then there are the speed/performance tests, which seems to place MEAN at or near the top as compared to the other mainstream web app stacks, which begs the question: is it possible that snide comments about "concurrency" are utterly beside the point? Who cares if my hoopty car looks inelegant if it wins the race?
As simply a learning tool for someone who is immersed in a .NET + jQuery stack every day, how does MEAN compare? I disliked Rails, fwiw. And since I'm becoming reasonably fluent in JavaScript, it seemed intuitive that building my own site from the Node-ground up wouldn't be a bad idea, purely for a learning exercise. Struggling through it right now, actually.
Can't be much slower than PHP or Ruby, so theres that. What is repelling to me is callback-hell and Javascript as a language in general. People will build simple stuff with this, then it will evolve, and then someone will have to deal with it. I don't want to be that guy.
[1] http://www.prahladyeri.com/2014/06/php-vs-node-js-real-stati...
[2] http://www.techhui.com/profiles/blogs/node-js-versus-rails-s...