This story is about not ignoring either sync or async...

It's great that the work finally led to both being supported. The cynic in me wonders if it's also async runtime agnostic, and not just Tokio. If that's possible.

What does this have to do with the article? The problem is for libraries: they want to support both sync and async use cases, without having to think about think about it, so that the user of the library can decide what is right for them.

My friend, did you jump to conclusions here? ;)