Why does Rust not have a standard async runtime?

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

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • rfcs

    RFCs for changes to Rust

    Rust used to have a built in green threading model - back before 1.0. But it was removed before 1.0. Basically it had too many downsides at not removing it would have forced the developers to keep its API forever as rust does not break backwards compatibility after 1.0.

  • may

    rust stackful coroutine library

    On the more extremely different side, there are people also using stackful coroutines in Rust, using may or lunatic. Because Rust doesn't force a particular async runtime, those experiments can try out very different APIs.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  • rust-lib

    Discontinued This library contains higher level Rust wrappers for low level Lunatic syscalls. [Moved to: https://github.com/lunatic-solutions/lunatic-rs]

    On the more extremely different side, there are people also using stackful coroutines in Rust, using may or lunatic. Because Rust doesn't force a particular async runtime, those experiments can try out very different APIs.

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