https://bugs.winehq.org/show_bug.cgi?id=42741
Claudio sick_soul@yahoo.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sick_soul@yahoo.it
--- Comment #71 from Claudio sick_soul@yahoo.it --- This affects Warcraft III too, in the exact same way (running wine-5.18 (Staging)).
This bug is a very good showcase of what is wrong in the way the Wine Project has been developing and handling issues in the now decades of development.
It has never been focused on applications, only on the general framework development, never considering applications as the focus.
The result is this, all Blizzard games broken, and it's business as usual.
Instead of proceeding with the constant refactoring and general development, this should have been marked as a "regression", the patch introducing the overarching framework changes _reverted_ until the regression was fixed,
instead of proceeding with the change and then leaving it to a few frustrated people to hunt enablement again.
This is completely backwards. I know it is hopeless (this is a 30 year project, so the minds are set), but a less _disfunctional_ project would treat regressions seriously (like the Linux kernel).
The kernel has a clear rule: "we do not break userspace. Enabling user space applications is the goal of the kernel, not anything else. Anything that breaks userspace is wrong by definition, and is a regression".
I wish for any functional fork of wine (be it Proton or other forks) could take and adopt this mindset, if the wine project is unable to.
Rant off,
CLaudio