|visits||member for||4 years, 4 months|
|seen||Jan 10 '14 at 22:11|
One of many people behind Adium and Growl, and author of many of my own apps (and a blog). Not an iPhone developer.
|bio||website||boredzo.org||visits||member for||4 years, 4 months|
|location||United States||seen||Jan 10 '14 at 22:11|
We have a large Ruby on Rails application (25 million monthly users), our management decided to rewrite in Node.js, am I crazy?
It's not just about CPUs. The reason why it's important to handle every request as quickly as possible (in a single-threaded system with no other concurrency) is because the server cannot service multiple requests at once, so every request has to wait until you've finished handling all of the requests before it. Concurrency, done right, means less waiting. Use of threads is not inherently a performance drain, and single-threadedness (by default or otherwise) is not a performance advantage.