Conversation

having looked at the relevant parts of tokio (uncountable layers of indirection) and mio (an abstraction built exclusively on top of undocumented native Windows NT APIs) i have concluded that i should only use async I/O in Rust in situations where i won't be the one debugging it
4
94
i may sound sarcastic but i am not. whatever the root cause is, i've spent probably more than 12 hours chasing down this one issue, and my conclusion? no workaround. can't use mio, can't use tokio, can't use hyper there's one reactor strategy and it's too clever for its own good
5
51
Replying to
wepoll and async-io seem to be simpler, but the ecosystem can't agree on a single abstraction around fd/handle registration, so they can't interoperate properly
1
Replying to
that is in fact what happened the problem isn't a windows license (pirating LTSC is a moral imperative) but the fact that in everyday interactions windows these days got less usable than late 2000s linux desktop
2
1
Replying to and
i've watched my roommate--a person whose technical skills i respect--spend several weeks trying to set up a dual booting nixos/win10 system with uefi i believe she's on the fifth reinstall from scratch, and having seen that breakage, i know i won't do much better, either
1
2
Replying to and
yeah I've tried it, hit an issue with PAT/MTRR and write combining ranges in graphical memory, tried fixing it, decided KVM it is (I might actually set up KVM with PCIe passthrough if wine doesn't work out)
1
2
Replying to and
I personally prefer having Windows on a totally different machine for gaming. For some reason I still have my better GPU in my workstation from back when I thought dual booting was a good idea but... that'll be fixed when I replace it with a new workstation.
2
Show replies