There's a ton of work being done at the compiler level to make Tokio more pleasant. This includes: 1. async/await. This is analogous to async/await in C# and E

There's a ton of work being done at the compiler level to make Tokio more pleasant. This includes: 1. async/await. This is analogous to async/await in C# and ES6, and should make the syntax a lot nicer. https://github.com/alexcrichton/futures-await https://github.com/alexcrichton/futures-await 2. Coroutines. This is the supporting technology for async/await. https://github.com/rust-lang/rfcs/blob/master/text/2033-experimental-coroutines.md https://github.com/rust-lang/rfcs/blob/master/text/2033-expe... 3. 'impl Trait'. This provides a way to say, "Look, my return type implements 'Trait', but the actual type declaration is way to tedious to write out, and anyway, it's private. This will help a lot with cleaning up complex Tokio types. https://github.com/rust-lang/rfcs/blob/master/text/1522-conservative-impl-trait.md https://github.com/rust-lang/rfcs/blob/master/text/1522-cons... At work, we use Rust, but we're avoiding using Tokio until these features land.