Hacker News Reader

>"It's a premature optimization that makes coding and debugging more difficult."

Going multi-threaded and dealing with semaphores and mutexes also makes coding and debugging more difficult. It's all about trade-offs.

View on HN

Generally true. Though, in context of webapps, each thread usually works on one request. If your threads share (mutable) states in that case then something is VERY broken.

Kind of, but consider logging. In node you can just console.log. In JVM you have to use a multi threaded logging library or your logs could be jumbled. Lots of things like that.

Those aren't the only ways to write thread safe code, just the oldest ways.

Also, remember that you can have unexpected re-entrancy at any callback boundary in the fully async model. It is not a panacea.

Reply on news.ycombinator.com