LaterRedditor,

Is there any risk of lawsuits from Microsoft for all these?

Chewy7324, (edited )

No, this kernel patch will be different to what’s in Windows code. It implements what’s necessary for wine to be more performant, not the actual Windows API itself.

Wine implements those Windows API/ABIs, which is legal because it’s done by reverse-engineering. I believe in some countries (US?) it’s also necessary for the devs to never have seen Windows code.

PS: Google v. Oracle is a US supreme court decision where Oracle lost at trying to patent Java API’s.

…wikipedia.org/…/Google_LLC_v._Oracle_America,_In….

ElectroLisa,
@ElectroLisa@lemmy.blahaj.zone avatar

What happened during the DiRT 3 benchmark lol, this game easily goes above 200 fps

NekkoDroid,
@NekkoDroid@programming.dev avatar

Those benchmarks under “Upstream” does not include esync/fsync from my understanding

mactan,

is this what used to be called winesync?

possiblylinux127,

Honestly this is the kind of thing we needed from React os. It would of been nice to be able to run the react is kernel in the background and then have wine make calls to it.

joojmachine,

I’m all in for performance improvements, hope to see this reach Proton ASAP

Chewy7324,

The patches are from CodeWeavers, and some of their work is cooperation with Valve, so hopefully proton gets those changes quickly. It usually takes a while before proton is based on a new wine release.

demonsword,
@demonsword@lemmy.world avatar

Windows NT Sync Driver Proposed For The Linux Kernel

Atemu,
@Atemu@lemmy.ml avatar

Proton would still need to make use of it.

demonsword,
@demonsword@lemmy.world avatar

yes, of course, but I was just pointing out that the proposed changes are mainly in kernel space, not in wine itself

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #