They could close everything except the kernel and maybe a few libraries here and there. The Linux kernel alone does not exactly get you close to having an Android distribution.

Mostly that it doesn’t work on Steam Deck. Hits memory limits IIRC.

Harsh words for someone who continues to be their client

I think the interesting thing about project 2025 is how specific they get over the plans. It’s not just what they want to do, it’s a plan for how to do it.

That’s such a weird claim

I’m pretty confident he’s not physically capable of that anymore.

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.

Hah! I wish it was email, so I could ignore it. Instead it’s either a Slack DM, which escalates to a phone call.

Clearly you meant:

string = "foobar"
length = 0
_ = [length += 1 for _ in string]
print(length)

Much more readable!

Edit: Damn, doesn’t work, was hoping to make something cursed but you can’t make an assignment during comprehension. Oh well, maybe Python 3.14!

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…

Also UI has to look good at either 720p or 1280x800. A lot of modern games don’t do that well at low res.

Because Stardust said “Get a Steam Deck and then you’ll see why” which makes no sense in the context of Denuvo DRM, hence it is most likely Stardust confusing anti cheat issues for DRM ones. Not that hard to figure out.

Well, in the context of the Steam Deck, DRM works fine and anti-cheats often don’t.