Linus’ apathy may keep ten different competing security ideas from each being mainlined, but it’s not impossible for them to continue and prove their worth out of tree until some sort of coherent best practices are established.

Meanwhile, actual security issues will continue to be patched as needed and Linux remains the most analyzed and targeted kernel in the world.

Look on my works Sim Mayor and

I agree, but I can envision scenarios where you are integrating into someone else’s workflow/machine and they (or their build system etc.) are expecting a shell script. Python is ubiquitous but sometimes you just want to work like everything else.

Seriously. I want a personal HUD for navigation and reminders that also corrects my vision (like normal glasses), not to become a walking surveillance device / info mine.

Yes. It has basically the same issue that any compatibility layer is going to have. It will either faithfully reproduce X11 so well it will bring all of the nonsense Wayland was meant to do a way with (everything not directly related to displaying graphics, like font and geometry rendering from the '80s, network transparency, insecure event handling) OR it will attempt to get a reasonable subset working for modern X apps and it won’t be compatible with dusty old binaries and X forwarding etc.

Right now it looks like a shim for Xwayland so it’s the first one, but as it matures we’ll see.

I couldn’t find the specific reasoning for this change, but I feel like QEMU is probably just too holistic to be appropriate for this kind of project.

QEMU needs to be able to emulate all the ARM hardware with enough fidelity to boot a naive operating system. For the purposes of running userspace applications almost all of that is not required, you really just need to convert one ABI to the other and translate the instructions. No need to handle firmware, the MMU, interrupts, disks etc.

Yes! It used to be so hit or miss with Wine, but I played WoW in it around the same time and it was crazy that it worked (at least most of the time).

There’s just no reason to do this work. Even if you ignore the fork’s controversial maintainer, and just favor the fact that it’s maintained at all (which is what the proposal’s author is suggesting) just… Why?

X11 is basically over at this point, why throw a last minute wrench into the existing, working Xorg infrastructure?

When we dropped XFree86 back in the day there were license issues, packaging issues and a real alternative didn’t exist - all justifying the effort to switch. None of these are a problem today.