As soon as he said: "The comparison I chose to go for is hard computation" I knew that node would be shown to be the loser. node isn't going to be great for lots of long computations - even node fans will tell you that.

We are finding node to be quite nice, though, for our real-time web app (which includes chat communication, and game like features). But we don't have any long-running calculations to do. I suspect that if we did we'd have them run in a separate server process... maybe even writing the compute intensive code in C++.

tl;dr: the type of benchmark chosen is stacked against node.