@Araq thank you. I was thinking about it, going to explore good old threads :).
> And the Erlang and Go approach have significant overheads that are > unacceptable for a system programming language. I understand and don't dispute that. My point is that async not a solution either. It gives neither pleasant developer experience nor reliable servers. I think it would be better to follow [this principe](https://www.solutionsiq.com/wp-content/uploads/2020/04/Skateboard-to-car-MVP.png) and just use good old threads. Maybe use some async to produce nice benchmarks, but not promote it as the main way for day to day web projects. I think the threads should be the main way (untill something better won't be ready). Threads won't produce impressive benchmarks. But it would be a better option for usual web projects than async. As far as I understand Nim Threads are more or less like Java Threads, and Java Threads while far from ideal, are successfully used in many projects for many years. It also would focus nim community on improving threads and its docs.
