mr_MADAFAKAWine 11.0 is planned for release tomorrow, featuring NTSync for improved NT synchronization, fully supported new WoW64 mode, enhanced Wayland/Vulkan drivers, and many other improvements
TrickDacy
Anafabula
mlg
mybuttnolieif proton is a few months behind wine in big updates, does proton-ge update faster? or is it a week or to behind proton
When will they finally add Copilot?
Once Microsoft has finished the transition of Windows into an Edge launcher with a Copilot backend…
IgilqFor most stuff wine is working better than on Windows. Thats why people actually import wine drivers to their real Windows install
Yo what people do that? Gnarly.
Die4Everfor Deus Ex Randomizer, we include the DXVK DLLs as part of the Windows installation automatically, because it runs better and smoother and with less issues
(we run vulkaninfo to check compatibility first, we check support for VK_KHR_maintenance6 or Vulkan 1.4 or newer, otherwise you don’t get DXVK)
https://github.com/Die4Ever/deus-ex-randomizer/blob/master/src/installer/Install/init.py#L123-L151
KneeTittsFor most stuff wine is working better than on Windows
So why dont any of my apps work then? Im super happy gaming is about 85% working, but in the apps space its got to be less that 40%
Wispy2891
Tobias Schmidl@inzen @mr_MADAFAKA as soon as the kernel rewrite happened, this is nearly guaranteed. https://augsburg.social/@schtobia/115767277911084452
Tobias Schmidl (@[email protected])
@[email protected] that's a really good idea - for #LinuxOnDesktop. Microsoft's biggest strength was it's WIn32 ABI compatibility - down to Win95. They are now seemingly willing to sacrifice this, in the first time in 30 years. Which means, there's a significant chance for #Proton / #Wine to be more compatible than Windows itself. Good riddance!
Oh wow, all the legacy software would be stuck on old windows or have to move to linux. If I got that right.
@inzen yeah, that would be terrible. https://www.youtube.com/watch?v=dYCXCqp1U5Y
That’s terrible! SNL meme clip
BarryThere was an update to that post, where the author said it was a “misinterpretation” and that it was just a research project.
@ashleythorne true! But the Win32 ABI was the "holy grail" of Microsoft. You can run a Win95 application written under Borland C++ today! That they even _considering_ of breaking that, would be *unthinkable* a few years ago.
For games it’s already better, I get a few extra fps on my low-end laptop with integrated graphics and the best part is that I don’t need to worry about games leaving traces/trash in the system as they are placed in individual prefixes
Except cassette beasts (for me) 😔
Literally saves are outside the Prefix for some reason. Apparently has to do with a heroic flatpak quirk 😒
I have an old mid range gaming rig and I also get improved performance on linux mint with steam proton
Should I switch from Wine Staging to stable?
Read this as Wine 1.0 at first lol
bufalo1973Does it work on ARM?
Running another uarch is a whole new level of complexity vs just running on a different OS but with the same uarch, especially if concurrency is involved because translating from one instruction set to another can break atomicity assumptions that concurrency depends on to maintain coherency. You’d need to do thorough analysis of the code to determine where special care is needed, and even then, it won’t be trivial setting it up in a way that avoids deadlock because you have to understand what the threads are doing before you can say if it’s safe for one thread to wait for another (since they could end up waiting for each other).
Whereas running code meant for a different OS just requires implementing that OS’ API (and behaviour, possibly including undocumented behaviour some code relies on, which can vary from application to application, hence windows compatibility modes where they add a translation layer themselves). Not saying this is trivial, but compared to the above problem, it kinda is.
Not that ARM support is impossible, just if they manage that, it will be proclaimed loudly, not something that requires digging. If they don’t say it supports ARM, just assume it doesn’t.
So an ARM ReactOS is more likely than an ARM Wine then, I guess.
Yeah, when you’re compiling from source code, it’s much easier to add in ARM support. Kernels do need to handle more hardware-specific stuff, like interrupt handling, context switching, feature enablement and the like will likely need custom ASM code and might have different parameters/events to handle. But at the user level, you can often compile for ARM by just changing a few command line arguments and it’ll be fine as long as you don’t rely on inline ASM and have ARM versions of any libraries you need.
You still might need to do some adjustments for specific behavior differences when it comes to concurrency and atomicity of operations. It didn’t surprise me to see that the previous attempt to make an ARM ReactOS didn’t support multi-threading, because trying to enable it was probably an unreliably buggy mess with race conditions all over the place.