I dunno, I think you may be underestimating ARM here. I’ve heard that the overhead from translating the machine code is a lot lower than you might think, because so much X86 code is optimized down to a RISC-like subset of the instruction set already. And if that overhead isn’t too daunting in the common cases, the more robust power management on the ARM side of the chip market might be able to make up the difference in a handheld environment for most users. Obviously it’s a huge amount of work to nail the software, and it would be on top of the work they were already doing on Linux, so I’m not saying it’ll definitely be in the next iteration, but I could definitely imagine it happening eventually.

It’s the “with which we are okay” that sounds a little stilted. Most speakers would probably phrase that part of the sentence as “which we’re okay with.” It’s just because “okay with” is so common that it almost feels like a transitive form of the verb “to be okay,” so splitting apart sounds odd.

Note that there’s already a different transitive verb “okay” which means “approve” or “authorize,” as in “the boss okayed your plan to use the forklift,” implying that the person doing this has authority or control over whether the thing happens. “I’m okay with it” by contrast typically means something like “I have no control over it but it also doesn’t trouble me.” “Unfazed by” (spelled in this way, not related to “phase”) would be a similar expression.

Kinda feels like moving out of America ought to be covered by my health insurance, really

Maybe they should patent it, to protect their TCP IP.

I don’t think it’s most yet, but it’s improving fast thanks to the Valve Steam Deck. Bazzite is probably the distro to look at for a machine that’s primarily for gaming; it’s based on the Steam Deck OS, but works on more machines. There are some high-profile games like Fortnite that won’t run on it, but a lot of stuff will, especially if it doesn’t rely on any fancy anti-cheat stuff.

Definite “Friday was the name of his horse!” energy here.

One issue is that it can be leveraged to maintain a monopoly. Microsoft famously made a bunch of small modifications to the HTML standard, so that web sites that wanted to work with MS Internet Explorer had to write custom versions to be compatible. But because so many people just used IE because it was bundled with Windows, those “extensions” started to become their own standard, so that then other browsers had to adopt MS’s idiosyncrasies in order to be compatible with the sites, which in turn harmed standardization itself. They even had a term for this technique: “Embrace, Extend, Extinguish.” It nearly worked for them until Google pushed them out with Chrome. Microsoft tried to do the same thing again with Java until the government got involved.

It’s complicated, certainly, but there are legitimate cases where “just a little tweak” can be quite a big problem for a standard.