Earlier quoted context omitted.
Wine's APIs are more stable than Linux's APIs, so it seems more plausible to me that Wine will become the first class target itself.
People always say this to shit on glibc meanwhile those guys bend over backwards to provide strong API compatibilities. It rubs me off the wrong way. What glibc does not provide is forward compatibility. An application built with glibc 2.12 will not necessarily work with any older version. Such application could be rebuilt to work with an older glibc as the API is stable. The ABI is not which is why the application w…
Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
61–70 of 512 posts
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#62Earlier quoted context omitted.
The grass is always greener on the other side - many low-level programmers feel like an imposter when it comes to high-level systems such as CRUD apps.
They don't. The "simplicity" of using a "high-level" framework for someone who bit-shifts for a living is almost comical.
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#63Earlier quoted context omitted.
They don't. The "simplicity" of using a "high-level" framework for someone who bit-shifts for a living is almost comical.
Really?
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#64Wine might be oddly self-defeating. Broad game support on Linux increases the viability of Linux as a desktop, which increases market share, which may result in developers creating Linux ports as a 1st class concern, which don't need Wine to run.
Unlikely. Games need a stable ABI and Win32 is the only stable ABI on Linux.
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#65Earlier quoted context omitted.
Most people? What mainstream Linux distros ship without fsync or esync support?
Well I can tell you that if it didn’t make it upstream Fedora didn’t ship it. It looks there was a copr for a custom kernel-fsync and projects like Bazzite or Nobara are adding patches. From my understanding the fsync patches were never upstreamed.
The point being that these massive speed gains will probably not be seen by most people as you suggest, because most Linux gamers already have access to either esync or fsync.
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#66Earlier quoted context omitted.
People always say this to shit on glibc meanwhile those guys bend over backwards to provide strong API compatibilities. It rubs me off the wrong way. What glibc does not provide is forward compatibility. An application built with glibc 2.12 will not necessarily work with any older version. Such application could be rebuilt to work with an older glibc as the API is stable. The ABI is not which is why the application w…
No other operating system works like this. Supporting older versions of an OS or runtime with a compiler toolchain a standard expectation of developers.
From a bit of research it looks like FreeBSD for example only provides a stable ABI within minor versions and I imagine if you build something for FreeBSD 14 it won’t work on 13.
Stable ABI literally only benefits software where the user doesn’t have the source. Any operating system which assumes you have the source will not prioritize it.
(Edit: actually thinking harder MacOS/iOS is actually much worse on binary compatibility, as for example Intel binaries will stop working entirely due to M-cpu transition - Apple just hits developers with a stick to rebuild their apps)
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#67Wine might be oddly self-defeating. Broad game support on Linux increases the viability of Linux as a desktop, which increases market share, which may result in developers creating Linux ports as a 1st class concern, which don't need Wine to run.
Wine's APIs are more stable than Linux's APIs, so it seems more plausible to me that Wine will become the first class target itself.
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#68Reading these posts always make me feel like an imposter. People are dealing with such low level things, while i'm outta here building simple CRUDs.
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#69Earlier quoted context omitted.
Well I can tell you that if it didn’t make it upstream Fedora didn’t ship it. It looks there was a copr for a custom kernel-fsync and projects like Bazzite or Nobara are adding patches. From my understanding the fsync patches were never upstreamed.
The common gaming-focused Wine/Proton builds can also use esync (eventfd-based synchronization). IIRC, it doesn't need a patched kernel. The point being that these massive speed gains will probably not be seen by most people as you suggest, because most Linux gamers already have access to either esync or fsync.
Re: Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains
#70it seems if you want the same on macOS, this is the place to contribute: https://github.com/Alien4042x/Wine-NTsync-Userspace-macOS-ba...
I mean, I know Mac has had some great games (eg. I spent so much time on school Macs playing that Bolo tank game) ... but they have probably <1% of the number of games Windows has. I'd expect a simiilar percentage of devs to be interested in Mace (or whatever you call Mac Wine).