zlacker

I may be the outlier but sync and async are both tools in the tool belt and ignoring one or the other is mostly silly?

>>fireyn+(OP)
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.

>>fireyn+(OP)
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.

>>fireyn+(OP)
My friend, did you jump to conclusions here? ;)

>>omgint+z3
I meant to more distill it like, any time you are making a choice between async or sync, you are making the wrong choice!