Jears

You will always need some sort of oom killer unless you have endless memory (or swap space, which comes with its own problems in the form of grinding your system to an almost halt). Imagine all memory is in use, then some system critical task (or even the kernel itself) needs memory as well. If the kernel can’t kill a less important process to free memory in such a situation you might just crash your system.

and you can afford to lose everything in the case of a power cut

But ext4 is a journaling filesystem, so a power cut shouldn’t harm it.

I have no idea about apple design guidelines and am not a UX designer, but wouldn’t a horizontal seperator look better? In gtk i would add one here, gives some extra space and more visual seperation.

So I don’t even use systemd myself I run OpenRC. Yet honestly I find the idea quite intriguing, having the service manager (PID 1) invoke the command seems like a cool idea to me.

It’s not really a sudo alternative as much as it is another way of doing something similar.

Wayland is a Display Server Protocol, meaning it is a specification of how a program wanting to display something like a window communicates with another program, the display server, which handles drawing to the screen.

It matters because it vastly simplifies and modernizes display server infrastructure.

X is huge, with many parts from the 80s and 90s that were simply not needed today, creating a fully compliant X Server with all extensions was pretty much impossible, which is the reason pretty much only X.org existed as a full implementation.

Some benefits for users are no screen tearing, VRR and support for more complicated setups like having multiple monitors all with a different refresh rate, which was a pain in the ass on X but is no problem on wayland.

X is going to die, especially with the fact that frredesktop and the two big DEs, GNOME and KDE are working on it. Some distros come with wayland by default already.