Hacker News Reader

The standard library currently only contains what is necessary to define _what_ a Future is. It contains no tools for actually executing them, and this is the role of Tokio.

View on HN

Very cool, so I can choose my own impl. Does Tokio have a true competitor today? From my cursory look at some projects, Tokio shows up everywhere.

There are some other executors too such as async-std, smol and bastion, but Tokio is the one with the largest ecosystem.

There's even been experiments with binding futures to glib or various GUI event loops!

I have also heard some talk on building executors for embedded devices where you can't allocate memory on the heap.

Yes, this was a big constraint on the design of the overall system; there's been a couple that have popped up.

Reply on news.ycombinator.com