linux versions are often low-effort ports. windows has low-effort console ports, linux has low-effort windows ports

Translating direct x to vulkan is often faster and more "native" than a native Linux build. Wine itself is a centralized single component with the almost the exact same libraries and workings that will never change much. Its very stable and the dependencies will almost always be the same because wine only fixes bugs and updates and accomedates new Linux drivers and patches.

Where as if devs want to make a build for Linux they have to make sure it stays updated and works for all sorts of different Linux packages which have different versions and different dependencies. Its why some programs made in python need an exact version of python and why python overall is shit because of it. Its a bad programming language with convoluted versions, modules etc. Same thing with Linux native builds in the simplest manner.

If your distro is missing ONE dependency the game won't run where as with wine its almost garunteed to run since its an all inclusive package with everything needed to translate .exe

In the most simplest terms or something like that

>>106509800
in the long run with the pajeeting of microsoft this will be true for windows as well
everyone's just gonna target wine because it's the only stable abi and we'll have wine-on-windows lol

>>106509840
isn't this pretty much what the
>run as windows 7 compatibility
thing is?

>>106509656
Part of the reason for that is Win32 is very stable compared to every other Linux API.
Win32 is so stable that even microsoft doesn't fuck with it and doesn't want to get rid of it regardless of the security issues that it has.
In fact I expect microsoft would rather find a way to containerize it than pull it out.

>>106509840
>we'll have wine-on-windows lol
A statement devoid of all signs of thought or brain function

>>106509960
>regardless of the security issues that it has
Such as?

>>106510127
>A statement devoid of all signs of thought or brain function
people already use winevdm on windows if they want to run 16bit windows applications on 64bit windows. and while not part of wine itself, people do also sometimes use dxvk on windows, too, which helps some games most notably gta iv

>>106510248
>using wine-associated projects means eventually wine-on-windows

>>106510327
winevdm is comprised of wine components, not wine-associated. it's wine's version of ntvdm packaged for use on windows, the 16bit subsystem in 32bit windows nt