Hacker News Reader

Web server programming is inherently multithreaded. I'm not sure if that's a convincing answer, but web performance is definitely a common rationale to use .NET or Java over Python or JS.

View on HN

Inherently parallel, sure. How often does that parallelism need to be within a single process? Not that frequently in my experience. If your threads aren't sharing state they can just be processes instead. If they are sharing state that's going to cause trouble if/when you have to scale beyond one process.

Programmers use frameworks that offer everything they need out of the box. They do need shared state for sessions. But they don't sit down and think if they're going to use threads or processes. They just choose a popular, feature-full framework.

Java and .NET frameworks use threads, rationale being threads perform better. I won't go into that discussion, even if I do have an opinion. Right now, I'm just pointing to what others say.

Reply on news.ycombinator.com