Rust async wasn't rushed, and pet theories for the one weird trick that would have made it work "correctly" are insulting to everyone who worked on it.
7
37
344
Conversation
It was literally the most drawn-out and hotly-debated feature Rust has ever added.
4
4
75
Honestly breaks my heart seeing those who pushed async all the way to the finish line slandered like this; in today's thread, and numerous threads prior, by people who are 100% wrong about the history and the feature itself.
2
2
81
Anyone can go on the internet and tell lies, and being smug armchair architects is a favorite bloodsport in our industry, but seriously shut up.
1
6
89
Replying to
Cross-platform async APIs in my opinion have one of the highest bars for running code and precise benchmarks next to a field like cryptography. They are notoriously hard to get right with tradeoffs everywhere
Quote Tweet
The kernel APIs are brittle and unforgiving and to the extent people can actually build cross-platform abstractions it's through blood, sweat, and tears.
Nearly every attempt I've seen to second-guess decisions made by people in-the-trenches has ended in a breakage.
Show this thread
1
4
AIO for storage is also a lot different than the best way to deal with sockets. Making a portable abstraction for any of this involves many sacrifices, and I think at this stage it's hard to end up with a result that's not disappointing for Rust's niche.
Quote Tweet
Replying to @DanielMicay @raggi and @thinkingfish
I don't think it's possible to have an AIO library that's both good and portable right now. The whole point of Rust is having efficient abstractions mapping well to the low-level details. If it's not a thin abstraction over io_uring, it fails at being a good AIO library on Linux.
2
4
It's much harder than usual doing it with Rust because you need to figure out how to enforce memory safety within Rust's model for it. A lot choices between different designs had to be made for Rust's type system / borrow checking and they aren't necessarily the best for this.