"Implicit in node is a fundamental rejection of traditional I/O. It’s pushing an asynchronous agenda with its event loops, based on the assumption that concurre

"Implicit in node is a fundamental rejection of traditional I/O. It’s pushing an asynchronous agenda with its event loops, based on the assumption that concurrency cannot be achieved with a thread per connection" This is actually very very wrong event based using kqueue/epool in 'modern operating systems' (read:monolithic/hybrid/posix) takes ~ 8 system calls while a threaded approach takes about 2/3 of that to do the same.