  oooOOOOOOOOOOO"
 o   ____          :::::::::::::::::: :::::::::::::::::: __|-----|__
 Y_,_|[]| --++++++ |[][][][][][][][]| |[][][][][][][][]| |  [] []  |
{|_|_|__|;|______|;|________________|;|________________|;|_________|;
 /oo--OO   oo  oo   oo oo      oo oo   oo oo      oo oo   oo     oo

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

racoon@lemmy.ml · 11 pts · 97d (1 reply)

[ removed ]

j5y7@sh.itjust.works · 3 pts · 96d

I'm ahead of the curve.

SapphironZA@sh.itjust.works · 21 pts · 97d

And its getting better more modern implementations. Not code from the mid 2000s that has been run though dozens of code translations and compatibility layers.

teawrecks@sopuli.xyz · 14 pts · 96d (1 reply)

I knew the article was going to mention NTSYNC, but is that really it?

I get that we don't want the argument for compatibility to effectively allow windows to define what the linux kernel has to looks like, but afaik this is one instance. The headline makes it sound like a systemic issue.

neclimdul@lemmy.world · 3 pts · 96d

I remember several decades ago when I dug into wine things asynch io was a thing there was a lot of discussion over. Apparently windows actually has a very robust asyncio interface that's emulated with a bunch of epoll and other logic.

I believe a lot of games did tricks with this and the hacks sometimes had performance costs.

A quick Google says that's still a thing being worked on and there's a newish io_uring but apparently that has problems. So maybe that's a place we can see improvements in the future.