> For the vast majority of web projects threads actually just add unnecessary > complexity leading to poor reliability.
Depends on the architecture. Async code can become very complex too and arguably is more complex than dealing with threads. > Furthermore I don't think you can just use threads and call it a day for your > web service. Spawning a thread per request won't scale. You need lightweight > concurrency which is what async/await in Nim is. Nobody proposed that, a thread _pool_ is used when you use `spawn`. I'm a compiler developer. The Nim compiler is CPU bound. The compiler might be run online, see the Nim playground. The last thing I want to do is to add `async` and `await` calls for things that may "block". For various reasons.
