It's the ultimate example of the “When you have a hammer, everything looks like a nail” phenomenon.
Is it the best alternative?
Erlang, as the article states, has some good things going for it; it's better than anything else that I know of for several categories of tasks. The problem is that other things are catching up, and while they may not be "as good", people can and will pick them if they are "good enough" and have other qualities that make them a good choice, such as being easier to learn.
Your comment to me comes across along the same lines of the people thinking digital photography would never surpass the quality of regular film. Maybe node.js won't be the one to catch up and pass Erlang, but my gut feeling is that something will. Scala, maybe?
At least Scala is in a similar category. Node.js is basically a bolt-on solution. It doesn't even actually have a comparable threading model, it just has a comfortably familiar one.
This project will be the first time many Javascript programmers will brush up against topics of scale such as these, and speaking as one, I'm definitely going to focus on Erlang to explore these problems. (but still play around with Node.js on the side ;)
In my mind this is a good thing because more people will realize some problems are too painful to solve in Node.js and they will take a hard look at Erlang. Or they'll get sick of the convoluted syntax hoop-jumping and they'll take a hard look at a Lisp.
I find JavaScript beautiful in a sense because in a very roundabout way it's pulling people towards more advanced PLs.
Pushing a simple solution to its limits is how people evolve to the next thing.