this post was submitted on 02 Aug 2025
43 points (100.0% liked)

Programming

22019 readers
329 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
43
\Device\Afd, or, the Deal with the Devil that makes async Rust work on Windows (2023) (notgull.net)
submitted 5 days ago by Kissaki@programming.dev to c/programming@programming.dev
5 comments fedilink hide all child comments
 

However, there are some important features that WinSock just doesn’t expose. […]

Rust’s current async ecosystem is built atop a particularly cursed concept. It’s an unstable, undocumented Windows feature. It’s the lynchpin of not only the Rust ecosystem, but the JavaScript one as well. It’s controversial. It’s efficient. […] Without it, it’s unlikely that the async ecosystem would exist in its current form. It’s called \Device\Afd, and I’m tired of no one talking about it.

top 5 comments
sorted by: hot top controversial new old
[–] PlexSheep@infosec.pub 12 points 4 days ago

I was so confused for a moment. AfD is the neo-fascist party of Germany.

[–] kata1yst@sh.itjust.works 15 points 5 days ago (2 children)

Windows is a marketing platform masquerading as an Operating System.

[–] Kissaki@programming.dev 2 points 4 days ago

I don't think these are mutually exclusive concepts.

[–] douglasg14b@programming.dev -1 points 4 days ago

Cool 👍

[–] soc@programming.dev 1 points 4 days ago

And all of this due to the mistaken design decision to stick with the obsolete readiness-based model instead of going with the superior completion-based model.

(You can build a readiness-based API on top of a completion-based API, but not the other way around.)