He proposed list of languages. And really, there's a lot of good languages to use on the servers. JS was never good language and we use it on the client-side just because it's the only language browsers know.

He doesn't explain why... other than ranting about the callback model (which has been in our desktops forever, most event systems rely on callbacks). The quote in the post has also misleading statements, NodeJs does scale in load and performance which is one reason why people use it instead of Python (which was one of the quote suggestions)

That was not one of his suggestions, unless you count stackless python. It was an example (i.e. twisted in python) in support of his point that callback's are a bad way to structure concurrent programming. His suggestions were Erlang and Go which are arguably better approaches in a purely technical dimension to NodeJS.

What his rant misses is that most technical decisions aren't made on purely technical merit for a host of different reasons.

>His suggestions were Erlang and Go which are arguably better approaches in a purely technical dimension to NodeJS.

I would say that it is based on a subset of the technical dimension. Maybe Erlang and Go might have nicer ways to handle concurrency flows but if it doesn't have a library X to communicate with backend component Y then there is a technical reason not to use it.

There is value added in identifying and clarifying a problem. It's partly how we, as a group, find solutions to bigger problems.

Identifying a problem is separate from coming up with a solution for all but the most trivial of problems.