Alternatives
Products that do what The cost of Rust async/await does
- 1CA
2019 · github.com
- 2AU
2022 · wishawa.github.io
- 3AT
2025 · github.com
- 4ME
2025 · github.com
- 5HA
2016 · github.com
- 6MC
2020 · github.com
- 7CA
2017 · github.com
- 8AA
2016 · github.com
- 9TC
2020 · npmjs.com
- 10RM
2025 · github.com
- 11AA
2018 · github.com
- 12KT
2016 · github.com
- 13AS
2018 · github.com
- 14PA
2014 · gist.github.com
- 15A1
2019 · github.com
- 16RI
2020 · github.com
- 17CA
I’ve been experimenting with building a Node.js HTTP framework using Rust + Hyper with N-Api. The project started as a fully synchronous server, but I recently patched it to support async (Tokio/Hyper). That change alone nearly doubled throughput in benchmarks. What’s different: * Built directly on Hyper, no heavy abstraction * napi glue for Node.js bindings * Minimal core (sync and async engines side-by-side) * Focused on raw performance, not plugins (yet) This is still experimental and not production-ready. I’d like feedback on: * Async API design — does it feel ergonomic? *…
2025
- 18NJ
2019 · docs.tardis.dev
- 19T5
2021 · tensorbase.io
- 20CA
2019 · github.com
- 21MD
2014 · github.com
- 22AA
2021 · supernormal.com
- 23AA
2017 · github.com
- 24AA
I wrote a minimal traceroute(1) clone that leans on asynchrony to reduce the time spent tracing a route. Underneath, it uses ICMP to do its job. The plan is to add support for UDP tracing and a path maximum transmission unit discovery mechanism. Comments and suggestions are welcome!
2022 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →