8 engineers on Hacker News describe using Tokio first-hand: 6 endorse it, 1 regret it, 0 are mixed.
“wrap it into tokio's async I/O, which isn't exactly well-documented (got to fix that)”
regret · production · chrismeurer · 2026-03-23 · source ↗ · wrong label?“It's now humming in prod doing its business.”
endorse · production · tuetuopay · 2023-11-07 · source ↗ · wrong label?“Everything worked great, including running a multithreaded tokio runtime.”
endorse · production · mcronce · 2022-03-17 · source ↗ · wrong label?“things were much easier to make work well on both counts with Rust and Tokio.”
endorse · production · Lorkki · 2021-12-23 · source ↗ · wrong label?“I've been using Tokio in a few projects and it has been a very good experience.”
endorse · personal · jgilias · 2020-12-23 · source ↗ · wrong label?“tokio uses less cpu consistently, even when compared to a cluster of the same size almost a year later”
endorse · production · jhgg · 2020-02-04 · source ↗ · wrong label?“makes working with tokio and futures so nice”
endorse · personal · silluk · 2016-12-24 · source ↗ · wrong label?“I do understand that the main source of my issues is due to ... using multithreaded async (via tokio).”
neutral · personal · gdcbe · 2023-12-21 · source ↗ · wrong label?