Yes. That atomized model of concurrency where your state goes everywhere and you somehow collect it back at some point was always (literally) the textbook example of how not to do it.
It was created to be an improvement over the Javascript situation, and somehow every language that had a sane structure adopted it as if it was not only good, but the way to do things. This is insane.
And yet, people are going to use async in Rust. The feature has already proven itself useful long ago in other languages, beyond the timespan a fad could survive. Everyone started out doing it the other way and got sick of it.
> concurrency where your state goes everywhere and you somehow collect it back at some point was always (literally) the textbook example of how not to do it.
can you tell why it is not how not to do it in your opinion? What are the obvious issues with this approach?
