I agree that this one isn't about async Rust at all. The main comparison is drawn in > And then fast forward a few years and you have an entire language ecosys

I agree that this one isn't about async Rust at all. The main comparison is drawn in > And then fast forward a few years and you have an entire language ecosystem built on top of the idea of making these Future objects that actually have a load of closures inside And this sentence is wrong. There's next to no `Future` implementations which are built on top of callbacks. And the reason why that's the way it is is exactly the one the author mentions: Callbacks don't work very well with Rusts ownership model.