It's just far easier to get a direct answer to what I'm looking for than going through mountains of SEO spam.

I congratulate SEO optimization companies on doing the very opposite of what they intended to do.

This is a problem with Linux on ARM generally (Android has had it since inception), it's not a Qualcomm problem.

This isn't fully the reason, Linux is infamous for requiring a specific build for each SoC (and usually each board of said SoC) where as Windows on ARM uses ACPI which Linux doesn't support to the same level. Linux prefers the landfill promoting device tree for each device approach.

Unfortunately apt/dnf isn't much better here because random tutorials online suggest people add random repositories where the creator of any repository effectively has root access to anyone machine that adds it as a remote.

At what point did I ever mention that?

The bar is pretty low, but the windows scheduler is aware what the currently focussed app is so it can prioritise not killing it.

On Linux? Not so much.

Far safer than a backdoor and no evidence.

But the slop in your comment here indicates you're arguing in bad faith.

Microsoft doesn't need to put in a backdoor on disk because they can make payloads that'll pass the TPM and not need a single trace on the disk.

Wayland at it's core is an IPC for sharing memory buffers containing surfaces around and details about those surfaces.

There is systemd the service manager/init system and systemd the project. An alternative service manager could add support for the formers unit files.