News for hackers. Stuff that matters.
Re:Async Rust doesn't have to be hard by bvrmn on Saturday June 04, 2022 @04:27AM (#31618165)
trio and stdlib has different primitives for sleeping/locking/garhering/etc. And you can't change loop implementation by simple ioloop_of_this_year.run(async_main) in the main().
Re:Async Rust doesn't have to be hard by linkdd on Saturday June 04, 2022 @05:33AM (#31618513)
This is nitpicking, I never said that.

There is still no explanation for what "mess" means, but I don't think it means having multiple competitors providing an implementation.

The fact that there are multiple async Python libraries means that the internals are generic enough to allow that. From what I understand of Rust, there could be another "tokio" as well. And they would not necessarily be compatible either.

This is like saying "You can't use a Django model with SQLAlchemy".