rain 🌦️

One of the ways I disagree with many of my esteemed fellow Rust people is that I think #async #RustLang is great. Switching #nextest over to #asynchronous Rust has yielded incredible dividends, including but not limited to what I described in https://sunshowers.io/posts/nextest-and-tokio/.

The ability to write cross-platform heterogenous selects provides an extraordinary amount of power.

BTW, now that I'm at @oxidecomputer, I've been trying out nextest on #illumos and it works with zero (0) code changes!

How (and why) nextest uses tokio :: sunshowers

How my open source test runner uses async Rust.

How (and why) nextest uses tokio
Dec 4, 2022 at 4:13pmWeb
Show threadA:\lex Dec 4, 2022
@rain Can't say that I've noticed an aversion to async in my Rust circles, but I agree that it is great. Almost all my Rust projects end up being async (mainly because my projects tend to be web sites/web services) and I find it an absolute joy to code in.
Show threadrain 🌦️Dec 4, 2022
@ilyvion There are real issues with async tbh: it's more complicated, the errors suck sometimes, currently requires learning about async-trait and pin-project, etc. I just think the benefits outweigh the costs by a lot
Show threadA:\lex Dec 4, 2022
@rain oh, absolutely; the ergonomics are still very rough around the edges and when you have to handle or implement Futures manually it can get a little hairy, but my overall experience is a positive one. Probably helps in the case of my own enjoyment that I'm somewhat of a Rust fanboy/fanatic.