4 ms·
I think I'm correct in saying you don't need tokio for async but it seems all non-toy code uses it. Are there any alternatives to tokio out there for writing re
by kingosticks 8y ago
I think I'm correct in saying you don't need tokio for async but it seems all non-toy code uses it. Are there any alternatives to tokio out there for writing real async code or is the idea to build everything on it? As if it was std, but it's not... right?
- bugmen0t 8y agoIf you need less abstractions over protocols, you might look into [mio](https://github.com/carllerche/mio https://github.com/carllerche/mio).
- steveklabnik 8y agoSorta, kinda. One big example of when you wouldn't use Tokio is when you don't have an operating system. Tokio is a good, default choice, but some projects may have different needs.
- bluejekyll 8y agoThere are systems that for various reasons can't use Tokio. In my own projects, I know there are people who need things to be generic across any executor implementation, as they can't use Tokio. Tokio itself is great though, so if you have no strong reason not to use it, I'd recommend it.