This guy works for red hat and his code is already constantly merged to upstream. His version is simply more bleeding edge. Also he's already somewhat famous in Linux gaming circles.
I have not needed any of these features to use proton on the games I own so I’m still none the wiser as to who the target is for this or what the context of this fork/its possible merging is
> I have not needed any of these features to use proton on the games I own so I’m still none the wiser as to who the target is for this...
...it's people who need these features and fixes? If you don't need them, then you don't need them, and you don't care about this.
With the addition of this comment, it seems like your commentary here boils down to "Why would I need this fork of this project that solves a specific set of problems that I neither have nor have bothered to understand?".
I do agree that it's reasonable to not waste time learning about problems you don't have, aren't really important if you don't have them, and that you're not interested in learning about, so don't make the mistake of believing that I'm throwing scorn your way.
It's interesting to read that an entire video streaming rework was done with AI, but likely won't be upstreamed because of the upstream policy on AI gen code. I wonder if that will ever be re-done using the plan GE outlined in the release notes.
Also really excited about this because there are several games that get kind of borked because they get stuck on an intro video before you get to the game menu without doing any winetricks.
> With all of that work done, I am happy to say all of the games listed above now have functional video playback with NO winetricks needed and NO dll overrides needed. No quartz,no dshow, no amstream, no lavfilters, no klite, no rsx3d, no wmp9, no wmp11, etc. -- All the functionality previously needed from those overrides is now patched directly into wine for the listed games that needed them, and the protonfixes that were previously added have now been removed since they are no longer needed.
It might come to be that maintainers have to begin accepting llm-authored or llm-assisted contributions just to maintain control of the project. Otherwise users will gravitate towards forks that offer the functionality they want.
They very specifically do not accept AI contributions because there is no way to tell if it's just regurgitating parts of the various Windows source code leaks from over the years ad-hoc, which would be a very costly mistake to make if Microsoft were feeling litigious.
That would be something Microsoft would have to prove in court and not that the AI came up with a similar approach on its own. ReactOS never got sued despite its similarity to Window's code.
Also not all Wine code is related to reverse engineering.
Or it might come to be that rejecting LLM-authored or LLM-assisted contributions becomes a badge of quality, and users gravitate to them to avoid buggy, inconsistent, or non-performant versions of the same software.
There's no need to guess, the reasoning is clearly laid out:
“Don't use an LLM tool to generate code. There's no guarantee
that the training material of that LLM respects our Clean Room
Guidelines, or that its output is compatible with the LGPL.”
Doesn't wine have various rules to remain a white-room implementation?
Not sure using LLMs which have possibly been trained on leaked Windows sources would be compatible with that. But that's just speculation, I wonder if LLMs possibly using leaked sources for training has been looked into. (probably legally difficult as the investigator would have to access the leaked sources too...)
...it's people who need these features and fixes? If you don't need them, then you don't need them, and you don't care about this.
With the addition of this comment, it seems like your commentary here boils down to "Why would I need this fork of this project that solves a specific set of problems that I neither have nor have bothered to understand?".
I do agree that it's reasonable to not waste time learning about problems you don't have, aren't really important if you don't have them, and that you're not interested in learning about, so don't make the mistake of believing that I'm throwing scorn your way.
> With all of that work done, I am happy to say all of the games listed above now have functional video playback with NO winetricks needed and NO dll overrides needed. No quartz,no dshow, no amstream, no lavfilters, no klite, no rsx3d, no wmp9, no wmp11, etc. -- All the functionality previously needed from those overrides is now patched directly into wine for the listed games that needed them, and the protonfixes that were previously added have now been removed since they are no longer needed.
Also not all Wine code is related to reverse engineering.
“Don't use an LLM tool to generate code. There's no guarantee that the training material of that LLM respects our Clean Room Guidelines, or that its output is compatible with the LGPL.”
--https://gitlab.winehq.org/wine/wine/-/wikis/Clean-Room-Guide...
Not sure using LLMs which have possibly been trained on leaked Windows sources would be compatible with that. But that's just speculation, I wonder if LLMs possibly using leaked sources for training has been looked into. (probably legally difficult as the investigator would have to access the leaked sources too...)