Rust's async isn't f#@king colored!

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Stream - Scalable APIs for Chat, Feeds, Moderation, & Video.
Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
getstream.io
featured
InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com
featured
  1. web-libusb

  2. Stream

    Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

    Stream logo
  3. rust-async-bench

    The cost of Rust async/await

    Rust's async story is zero-cost in the sense that it is not possible to implement a better asynchronous state machine than the one the compiler will provide for you, but it is explicitly not zero-cost in the sense that there is no overhead to asynchronous execution in comparison to synchronous execution. See experiments like this for examples.

  4. proposal-top-level-await

    Discontinued top-level `await` proposal for ECMAScript (stage 4)

    There is a proposal for top-level await in JS. I'm guessing this would effectively kinda do the same thing? Or am I wrong there?

  5. async-std

    Async version of the Rust standard library

    Async in rust needs a runtime (aka executor) to run. You can maybe get a better description from the rust docs. As an example, Tokio attempts to provide an interface for a developer that is minimal change to the more common blocking code. So you'd end up putting #[tokio::main] above your main function to spin up the executor and most of the rest of the code is similar to a non-async version with a few sprinkles of .await, which you can see in the hello world for tokio. In contrast, async-std provides a more hands-on/low-level approach. If you are unlucky enough to have libraries that choose different stacks to work on, you'll possibly (probably?) have to handle both.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • What is the best way to ask for user input while simultaneously outputting to the console?

    2 projects | /r/rust | 16 Jan 2021
  • async-std v1.9.0 has been released!

    2 projects | /r/rust | 15 Jan 2021
  • How to Read Data from PostgreSQL with Diesel in Rust?

    1 project | dev.to | 11 May 2025
  • Rust async is colored, and that’s not a big deal

    4 projects | /r/rust | 14 Mar 2021
  • Show HN: Whirlwind – Async concurrent hashmap for Rust

    6 projects | news.ycombinator.com | 5 Nov 2024