Its cool, but it also means the development of the language is very very slow. Async is still half backed and super complex, and I say that as a guy who has written rust code 40h/week for the past 3 years.
This isn't why development is slow. In my opinion, if I were still employed to work on Rust improvements to async would have shipped a lot faster. My blogging about it in my free time is my effort, in light of my circumstances, to get the project back to shipping on async.
It would help for sure to have a lead on this. Still there are a lot of opinions on the way forward for async so it would still be slow I think.
I did get annoyed recently by the trait async stabilization that promised us a good trait-variant [1] which has been abandoned. Makes it so much harder to build a library without it.
I fully agree. Sometimes it feels like so much effort is put into rust's async side that the rest of the language ends up taking a back seat and suffering for it.
Rust dev team cares too much about async and webdev imho. Yes I know the web is where 95% of programming jobs live now. But as a C++ systems programmer I simply could not care less about the web. Rust is a systems language trying to get its foot in the web door. I'd selfishly rather it focus on being a superior C/C++. Alas.
The nature of open source is that people work on what they want to work on. People work on async because it interests them. But to the same level many people in the lang and libs team don't know async that well. You may perceive it that everyone works only on async but this is just not true.
