Of course.

Yep. I’m Linux at home but macOS all day at work. My employer won’t let us use Linux workstations (despite everything I work on being Linux…). Both are vastly superior to Windows.

As someone who works fairly extensively with all three major platforms… You’re definitely wrong about macOS here. Almost everything on GitHub that works on Linux also works on Mac, aside from GUI applications which are often more OS dependent. The readme pages often just lump Mac and Linux together as they can be pretty similar, especially for things written for interpreted languages (python) where it’s often literally the same.

It would allow them to do HDMI FRL also, which is probably what you mean when you say HDMI 2.1. AMD cards also do HDMI FRL I thought. FRL is what allows things like 4k120Hz (higher bandwidth modes). The VRR that the Dock does is the VRR standardized with 2.1, which is why it works on TVs and devices that do not support freesync (see: LG TVs).

Anyway, the Dock doesn’t have a fast enough HDMI converter to do that. It’s not a licensing issue. Next gen Deck/Dock will probably do it.

Actually it works fine on Steam Deck. It uses VRR over DP to the dock, which then translates it to HDMI with VRR. The dock has proprietary firmware to do this.

Intel and Nvidia hardware with open source kernel drivers also do a similar trick where the HDMI part is in a firmware blob. Only AMD does not work with HDMI VRR.

Exactly. That’s why it’s a trash motherboard as soon as root access is gained. It can never again be trusted.

How do you trust that the flash was done properly if you did it from the compromised system? This would only work if you flashed it externally somehow without the system running.

You’re supposed to put in GitHub usernames, not full names.

Yes it is. It’s not in mainline wine, it’s been in kernel for a long time now.

It’s annoying all the articles are focusing on performance versus stock wine here when basically everyone uses Proton or a fork of it anyway, which has had fsync for years now that does similar performance uplift.

The story here should be that we’re getting fsync level performance with fewer bug and it can be upstreamed to wine. There is no relevant performance uplift for Proton users, but I guess performance gets clicks so that’s the story all the press are going with.

It’s not merged, but the benchmarks are against upstream wine. Proton has hacks (fsync) that have almost identical performance uplift but were not suited to upstreaming.

So basically this will improve “correctness” versus current Proton, not performance. Should fix some bugs and improve compatibility.

Versus stock wine, it’s a huge perf uplift though.

Technically AMD also offers an open Vulkan driver (AMDVLK), it’s just dog shit, and an open compute driver (Rocm), its just also bad, and an open OpenGL driver (Radeonsi), which is solid.

Those three are all primarily developed by AMD engineers and are fully open. Nvidia has no such open equivalents.

Uhh nvidia has had native Linux drivers since the 1990’s…

That also doesn’t resolve the carrier seeing which IPs you’re connecting to, which can often be traced back to services or sites.

The addresses themselves that you’re connecting to as one example. Also often DNS.

As a father I can confirm this seems right

No, it’s a layered model like Docker. They depend on various images that can be shared across applications targeting the same runtime.

No no no you don’t understand. The war in the rest of Europe will be just beginning, but the war in Ukraine will be over.

Source?

Yes, but it is Linux. OP doesn’t mention GNU.