Lets not forget that process-per-connection has a really bad performance rep. These newfangled non-blocking designs are seemingly much better for everyday task

Lets not forget that process-per-connection has a really bad performance rep. These newfangled non-blocking designs are seemingly much better for everyday tasks. And saying that an async IO server is a bad choice for computational things is, well, a well-known tradeoff that 99% of apps don't have to worry about. When was the last time someone complained that their webservers were CPU bound? Its always the DB that is the bottleneck...