Re:Xbox goes down. You can't play games you own on disc
by inigyou on Tuesday August 04, 2026 @01:31PM
(#49172093)
At least it has async I/O, unlike Linux.
Re:Xbox goes down. You can't play games you own on disc
by bigfishrunning on Tuesday August 04, 2026 @04:30PM
(#49174639)
not sure if I'm missing something, `select` seems to work just fine on my machine
Re:Xbox goes down. You can't play games you own on disc
by inigyou on Tuesday August 04, 2026 @04:52PM
(#49174982)
but `select` is not async I/O
Re:Xbox goes down. You can't play games you own on disc
by cyberax on Wednesday August 05, 2026 @03:52AM
(#49179813)
Windows NT kernel is a marvel of engineering. It's incredibly flexible, you can build crazy stuff on top of it without having access to its source code.
As an example, Parallels had a version of Docker-like containers on WINDOWS in 2006! They implemented it as a wrapper on top of the native Windows NT kernel API.
But the downside of this flexibility is relatively slow filesystem operations. It was a conscious trade-off from Windows kernel developers, they thought that flexibility was more important.
Some other things have been baffling over the years (but I belive they are now at least somewhat solved). For example in Windows 7 and older Windows would spend tens of seconds on "installing drivers" for a USB stick every time a new stick was inserted (or even an old stick inserted into a new port). I don't remember seeing this on Windows 10 (or 11), but I barely used those.
But yes, compared to the userspace the kernel is way less jank. (Like how Windows Updates takes minutes to run to conclude that there are updates, and dozens of minutes to install them, while pacman -Syu on Arch can be done in second if there are no updates, and maybe 2-4 minutes in the worst case of a kernel update with dkms modules being rebuilt.)