[nobbyclark]

Waaaaiit a second! This "async thing" is not a fad created by node.js but rather the effective conclusion of the C10K problem - http://www.kegel.com/c10k.html - that we could scale up our application servers to handle more requests and that threads alone had failed to get us there.

And sorry anyone who wants to claim that Java's green threads are somehow a better programming model than async IO ala node.js + promises is pretending to write code. Yes async IO is not easy, certainly nowhere near as simple to manage as process / fork but with consistent coding style your can still end up with a system that behaves predicably and most importantly can be reasoned about.

Meanwhile I bitterly regret the days and weeks of my life lost to debugging threaded code. Never again!

[zhong-j-yu]

One-thread-per-connection is very bad. But one-thread-per-request is probably not that bad.