Node.js cures cancer
I like how every rebuttal turns into "how fast can you compute a fibonacci number". I was looking for a function that burned a nontrivial amount of CPU, the choice of fibonacci was arbitrary. Let's move on from that.<p>What I was showing was that if your request handler does a nontrivial amount of CPU work, it will hold up the event loop and kill any "scalability" you think you're getting from Node.<p>If you Node guys were really that irritated by this, you're going to be super pissed when you learn how computers work.<p>I ain't even mad.