> the compositor then composites them together. to me, that feels more like the kernel is at the center of the diagram here: the wayland compositor is between the kernel and the output / input.

It's also possible to use hardware planes to get the actual graphics device to composite for you directly from its video memory, effectively reducing latency to the lowest possible.

Pretty sure Deepins DE uses this model

This has nothing to do with Wayland, only a poor implementation of a display server running a Javascript shell, namely called GNOME.

> If you want that start your processes as different users.

How does this make any difference if they're going to connect to the same IPC that handles input/display?

The display server must absolutely enforce some kind of security boundary between clients. Clients that are running untrusted code (e.g. a web browser) must not be able to hijacked into controlling a potentially privileged client (e.g. a root terminal).

If you reinvented Wayland, there's little reason you would t get the same thing.

The "limitations" are political, not technical.

The instruction set is not the issue, the issue is on ARM there's no standardized way like on x86 to talk to specialized hardware, so drivers must be reimplemented with very little documentation.

That has nothing to do with running VMs.

The monarch being Commander in Chief is ceremonial. Everything is done on the advice of the Prime Minister and their cabinet.

The chance of the monarch overriding said request is less than 1%.

Even then, parliament is sovereign. Whilst the logistics are complicated due to how things are introduced to the house, if parliament says no to a prime ministers decision, it overrides anything the prime minister who has no absolute power like a president does.

Monarchists can't have it both ways, though. Making him a ceremonial CiC isn't going to provide you with much of a bulwark against abuse of power by parliament. Or he isn't ceremonial and he could become a threat himself.

It has? Many distros have it enabled by default, too. The article discusses it quite a bit.

It did, there's two incompatible approaches, zram and zswap.

Windows will also prioritise to keep the desktop and current focussed application running smoothly, the Linux kernel has no idea what's currently focused or what not to kill, your desktop shell is up there on the menu in oom situations.

The same behavior exists as far back as NT4 Server, which does not provide a foreground priority boost by default.

You can control your phone, it's just your bank won't allow your phone to store EMV keys if it's a non-locked down environment.