Reactor-based framework versus Node.js streaming

"I found something faster than Node.js"<p>Why do people treat this as such a discovery? Where did Node claim to be the fastest solution to everything?<p>The only answer I can think of is that people feel threatened by node.js for some reason, and constantly feel the need to criticize it for not being the best at everything.<p>If you want to serve a 1mb file a million times, without caching it, or using sendfile, yeah, node will probably be slower compared to other things. It gets really old seeing posts like these.

Having seen this kind of articles over and over in the past, I can't help but wonder why people keep on producing benchmarks to evaluate the capabilities of different servers/languages/frameworks/designs.<p>Unless the person producing the code or setup for the comparative benchmarks is an expert in all the fields he's comparing and handcrafting every single byte to perfection, it WILL all boil down to respective members of said communities pointing just how skewed, unprofessional and unfair the benchmark is.<p>There's no value to extract from such poney shows most of the time because it generally reduces complex concepts to mere numbers and metrics, with the additional task of managing to handle all the different setups, flags and whatnot in a way that doesn't create an outcry.

Interesting, but how is this different than Netty?<p>I'll admit, netty's interface is annoying, but that aside, from a perf perspective does this offer anything?

Just contribute to Netty, Finagle or Akka depending on the style you like.