smol

My understanding is you always need a runtime to play the async game -- something needs to drive the async flow. But there are others on the market, just not without the.. market domination... of tokio. https://github.com/smol-rs/smol looks promising simply for being minimal https://github.com/bytedance/monoio looks potentially easier to work with than tokio https://github.com/DataDog/glommio is built around linux io_uring and seems somewhat promising for performance reasons. I haven't played with any of these yet, because Tokio is unfortunately the path of least resistance. And a bit viral in how it's infected things. But I'm planning on giving glommio at least a whirl.

Smol is essentially that iirc. https://github.com/smol-rs/smol Though I have not used it extensively.

> There's at least one other popular one of note. The other popular runtimes are async-std [0] and smol [1]. [0]: https://github.com/async-rs/async-std [1]: https://github.com/smol-rs/smol

This is a reasonable overview with a few caveats - Warp seems to have one of the better api experiences but has significant performance issues. In the async world I think https://github.com/stjepang/smol is going to have a pretty big positive impact on the useability of the whole system so I wouldn't rush to go all in on either async-std or tokio just yet. Last I read it was still having some fairness issues that were next to fix though. There is also https://github.com/withoutboats/ringbahn Which is very disruptive in that io-uring doesn't have a natural async interface?

I would really like to print out stjepang’s library smol. It’s just a few thousand lines of code and I have a feeling that it would be easier for me to understand on paper. How does anyone do this? I’ve heard that companies sometimes do code reviews on paper, so I figured this would be a solved problem. Still, I couldn’t find a decent solution anywhere. So there’s the question for Ask HN. How in the world does anyone print code in a reasonable way? By “reasonable”, I mean: 1. with line numbers, 2. with syntax highlighting, 3. and preferably some sane separation of source files. Smol: https://github.com/stjepang/smol

From the article: > Because our code winds up running in other people’s apps we don’t use a full-fledged async runtime like tokio or async-rs since those are optimized for “use all available resources” scenarios like network servers or client applications. Have you considered the recent alternative, smol [1]? Do you have any plans to share source or build scripts for the glue components? How have you been able to incorporate native functionality such as media codecs and screen capture with shared logic written in Rust? Has Rust worked well when you also need to integrate with runtimes such as React Native or Flutter? [1] https://github.com/stjepang/smol