Conversation

Jan 21, 2018

For giggles, writing a data store backed by #etcd in #rustlang. Having a ton of fun and learning a lot, though still fighting with the compiler and borrow checker. Also, #tokio is freaking amazing. /cc

How was tokio compared to Go's goroutines and channels?

Kevin Hoffman

@KevinHoffman

Jan 21, 2018

They solve different problems. Tokio as the name implies is focused on i/o whereas channels and goroutines are general purpose async. Tokio feels like the best LEGO set for building async apps. Composable arch is sublime

Replying to

and

I'm guessing the better goroutine comparison would be futures+generators+some sort of thread pool to run them on. More flexible, but more choices for the dev to make, and easier to make something that blocks the execution of other work. You also then need Tokio to do any IO.

5:25 AM · Jan 22, 2018Twitter Web Client

Replying to

I like the flexibility, but at the moment the ergonomics and error messages still need improvement. That's on the roadmap though - async/await and impl Trait will both make things much cleaner and easier to work with.