> io_uring for example gives an entirely different model, one with some lovely performance benefits. The io_uring model is also fundamentally async? So not sur

> io_uring for example gives an entirely different model, one with some lovely performance benefits. The io_uring model is also fundamentally async? So not sure what you’re arguing here. It’s just completion, rather than readiness based, but otherwise no different, and completely compatible with how other async things work in the Rust ecosystem (see tokio-uring). If anything, I’d argue that io_uring is the best example of the benefits of async API’s over the “just spawn another blocking thread bro” model.