> So what's your point? I picked a real world example aligning well with alexeypetrushin's requirements:
* Code is developed synchronously first. * Code is then migrated to run on a server, rewriting code is expensive. * Even if a rewrite is feasible, all your dependencies need to run asynchronously too. You said > For the vast majority of web projects threads actually just add unnecessary > complexity leading to poor reliability. And I'm challenging this "vast majority" claim. We shouldn't be shy to tell our users about the `spawn`'ing server solution. Nim has both great async and great threading support -- we currently lack a great _integration_ between these two, and while we're making good progress on this problem, in the meantime for production usages we should encourage people to try both solutions and see what fits their use cases better.
