Quoting: whizseOh, this might be bad. Seems like an inside job by the new'ish maintainer:

https://boehs.org/node/everything-i-know-about-the-xz-backdoor
https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27

If so, someone needs to go through xz-utils with a fine toothed comb.

QuoteI really hope that this causes an industry-wide reckoning with the common practice of letting your entire goddamn product rest on the shoulders of one overworked person having a slow mental health crisis without financially or operationally supporting them whatsoever. I want everyone who has an open source dependency to read this message https://www.mail-archive.com/[email protected]/msg00567.html

Quoting: pilkI'm glad they're finally doing this, but this should've been implemented, at the very least, after the first time this happened.

Quoting: Eike

Quoting: pleasereadthemanualYou see, it's actually really simple.

(...writes a manual...)

Quoting: Eike

Quoting: pleasereadthemanualI get the distinct feeling I'm missing something...

(Serious) question: Mesa?

Quoting: Marlockthey could delay SDL3... but that only helps if Wayland devs clearly signal they'll solve their end of the issue soon with high priority... which seems a bit unlikely, though Valve does have plenty of people working for them on both things, iirc

Quoting: hell0

Quoting: pleasereadthemanual

QuoteIf we do this, we are basically accepting these issues are unfixable for the next ten years (SDL4).

[...]

Shipping a broken default is the wrong thing to do. Unfortunately, that protocol is unlikely to be finished before SDL3's release (3+ months away).

Two bad options. There's suggestions of flipping the default later on in the lifecycle of SDL3 once this protocol is implemented, and that seems like what's going to happen. I'm not sure what the downsides of this are.

I'm not interested enough to go and read the whole debate. But is there really a 10 year life cycle for SDL? Or something preventing them from releasing SLD4 a year from now?

QuoteMike Sartain for incorporating SDL into Team Fortress 2 and cheering me on at Valve.
Pierre-Loup Griffais for his deep knowledge of OpenGL drivers.

QuoteEverybody at Loki Software, Inc. for their great contributions!

QuoteIf we do this, we are basically accepting these issues are unfixable for the next ten years (SDL4).

Quoting: CalebQ42Good to see this is finally being fixed(ish). This is one of the main reasons I switched to AMD nearly a year ago as the issue ultimately comes down to NVIDIA deciding they want to do something a different way then everyone else and letting their users have a bad time. From the research I've done, there are some benefits to explicit sync over implicit sync, but since every other driver already has implicit sync no one was in too much of a rush to add it.

QuoteExplicit synchronization is the future of graphics and media. At
least, that seems to be the consensus among all the graphics people
I've talked to. I had a chat with one of the lead Android graphics
engineers recently who told me that doing explicit sync from the start
was one of the best engineering decisions Android ever made. It's
also the direction being taken by more modern APIs such as Vulkan.

Quoting: LoftyHow is it different from emulating lets say a 20yr old PS2 game ? perhaps fundamentally it is not that far apart, but the developer is not losing money on sales for a start, the hardware is well and truly out of action and there is no effective DRM to bypass or machine to crack. Maybe that's just semantics.