News for hackers. Stuff that matters.
Re:A four year plan for async Rust by the__alchemist on Tuesday November 07, 2023 @11:57AM (#38179305)
> the kind of ... service that benefits from using non-blocking IO.

Async, in the sense from the article, and non-blocking aren't synonyms. Not using Async doesn't imply blocking.

Re:A four year plan for async Rust by withoutboats3 on Tuesday November 07, 2023 @12:00PM (#38179356)
What Rust libraries use non-blocking IO without using async syntax? I don't know of any. This interpretation of the request is new to me: I've exclusively heard complaints about libraries using async from people who want to use blocking IO.

(Also, in case it isn't obvious: I wrote the article in question.)

Re:A four year plan for async Rust by the__alchemist on Tuesday November 07, 2023 @12:05PM (#38179460)
I usually do non-blocking ops with hardware interrupts, DMA, distributed computing (over CAN etc), and multiple cores. For GPOS/Desktop PCs, threads, SIMD (GPU or CPU etc) are effective.

More generally than the concurrency operations I described, are any sort of event-loop or state machine, of which Async is one example.