this post was submitted on 25 Sep 2023
33 points (97.1% liked)

Rust

6130 readers
45 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
 

All these posts about async are making the freedom to choose our runtime seem like a bad thing.

For most people, we can just accept Tokio as the de facto standard, and everything is good. Having the other runtimes only makes things better. Don't do anything weird and it won't be too much work if you need to change.

Any big change you miss is bound to either be implemented in Tokio or be too different for any abstraction to save you from the work.

If you're writing a library that you want to be reusable by everyone, I understand your frustration that it's not easier to make it universal for all async runtimes. You can still choose one, minimize the code you would have to change to implement others, and appreciate that in almost every other programming language you don't get more than one async engine anyway.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 year ago* (last edited 1 year ago)

I stopped worrying about this when I had a project with two async runtimes (tokio and bastion) and it worked fine without any special setup.