While this is still a massive problem, it does require a public fork at some point. So if you have a private repo that has never had a public fork, you should be safe.

From my own looking into this it looks like more of a suggestion than a request (for now at least), just a “this might be a good idea, we should look into it”.

The deleting most emails is very interesting. In my personal email, I’ve been saved quite a few times by finding emails multiple years old. But I can definitely see how things would be quite different in a work email, and I may consider trying that myself.

Linux may very well not be for you, but using Arch first is like jumping into the deep end to learn how to swim. It’s no surprise you’re drowning. I’d recommend you try a gaming-focused distro like Nobara before you go back to Windows for good.

Oh yeah, to be clear I don’t think Macs can’t be good gaming machines, it’s just that it doesn’t seem to be heading that way right now.

Windows has one major thing going for it: it’s best-in-class for gaming. It might even be the greatest gaming platform of all time. Linux and even Mac are gaining ground, but they’ve got a little ways to go.

…is Mac gaming actually gaining ground? From listening to a friend of mine who has a Mac, it sounds like Mac gaming is going steadily backwards. Wine and similar doesn’t work very well for them, and Mac compatibility is happening with fewer and fewer games. Game Porting Toolkit isn’t really for end users, is it? Is there something else my friend is missing?

The issue is one of licensing, not technology. There’s all kinds of patents in the space, and using free codecs could still infringe them. DirectX doesn’t have the same patent protection. I believe in theory you could make a fully open source Linux native version of DirectX.

For more info from someone who knows more than me, see here.

Well, sometimes Windows games depend on propietary codecs, and until Valve can get the devs to make adjustments so the codecs aren’t needed, the games aren’t going to work properly in regular Proton.

If GE received a Cease and Desist, that would be frustrating, but linux gaming would go on. If Proton got a Cease and Desist, that could be catastrophic to linux gaming. Valve could even theoretically get banned from working on linux gaming (like the Yuzu devs got banned from working on emulation). It’s just not worth the risk for compatibility/performance for a smaller proportion of games.

This isn’t binding tho, Adobe could change their minds in a year and then legally train an AI on all the data they’ve collected. Their own blog post doesn’t even preclude that, their AI language is present tense. In addition they could just license the data to other AI companies.

This is a great list of USB wifi adapter chipset compatibility.

That’s fair. It’s an all-around sucky situation regardless, and it makes sense why AMD isn’t marketing socket longevity quite as much in AM5 as they were with AM4.

I do think losing capabilities for older CPUs in favor of new ones is pretty common for long lived sockets, and is an acceptable tradeoff for longevity imo. The board I was originally using for a 2600X never promised 5000 series support, but almost added it anyways. Unfortunately it never got beyond a beta bios, and I decided that wasn’t good enough for me (and I ended up giving the old mobo to my sister in a build for them, so it all worked out anyways).

How did you know the CPU wasn’t the problem? Sometimes CPUs have defects. Especially given the underclocking seemed to help.

Just to clarify, a few airplanes still use leaded gasoline. The vast majority do not.

Nvidia already opened their driver, at least to the same extent as AMD, which is why NVK is able to exist.

I’m not sure about the latter

I believe it was Xwayland 24.1 that recently released that brought explicit sync support, so you’ll need that.

Seems like a good redesign.

I believe that the custom for a lot of wine patch notes is just to mention the first application reported with the bug even if it affects many applications. So that could be what’s happening here.

will not solve issues with compositors not having it

Many compositors already have patches for explicit sync which should get merged fairly quickly.

graphical libraries not having it

Both Vulkan and OpenGL have support for explicit sync

apps not supporting it

Apps don’t need to support it, they just need to use Vulkan and OpenGL, and they will handle it.

Wayland doesn’t implement sync of any kind, they probably meant to say “the Wayland stack”

Wayland has a protocol specifically for explicit sync, it’s as much a part of Wayland as pretty much anything else that’s part of Wayland.

Nvidia is not the only driver that needs to implement explicit sync.

Mesa has already merged explicit sync support.

The reason is 24.04 is LTS, and they want to keep things more stable, even if that means more bugs. 24.10 should come with 6.1 in the fall.