Some musings on the async ecosystem and compatibility between async-std and tokio... 1/15
Yeah, it's a sad state of affairs. I'm suggesting some workarounds for self-contained async crates and I'll also admit this is not always a viable solution. But, async-h1 did figure out a simple, runtime-independent solution for HTTP clients and servers, which gives me some hope.
-
-
I’m thinking once the async craze dies down we will be somewhere where the world looks a bit different. Don’t think picking the excecutor will be our problem in two years. One ecosystem will win.
-
I hope not. In fact, I want to build a world where we have thousands of different runtimes. :) One of the core design goals behind futures is that they're executor-agnostic, and has always been. If we end up with one executor in two years, we failed on that goal.
- 3 more replies
New conversation -
-
-
I’m pretty disillusioned now that this will work. I also can’t to realize that polling of futures is s bad model for a lot of situations :(
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.