Is there enough room for two asynchronous io frameworks in Rust?
I’ve spent a bit of time with
rotor for io clients, and have found it great once you get over that (significant) cognitive barrier to entry. I’ve found it works best when you don’t try to compose too much in a single loop, so I feel it’s given me the tools to write a high performance connection pool that is abstracted away from users, and works well with
tokio is a thing, which I haven’t started with yet but it looks like it’ll be much easier to compose. Does anyone, like @seanmonstar, have experience with both platforms and can outline their thoughts on what works well in either, and whether they see a future for both?