dpkg-reconfigure sysvinit
I don't remember what I was trying to achieve, but it was a bad idea. I also didn't (and still don't) know how to fix the outcome of this, so - since my home was on a separate partition anyway - I just reinstalled Debian since that was much quicker anyway.
Thank you for explaining what Wayland really is: a protocol. I see way too many people in forums going "Wayland constantly crashes" or "this doesn't work with Wayland" but what they actually mean is that their compositor of choice crashes or lacks a feature. There are a few things that Wayland doesn't support (like multiple-main-window-apps that want to put their children relative to each other (i.e. multi-window Gimp)), but that's usually not what's being discussed.
But please allow me to correct you on a few details:
X is commonly available as a shortcut to start the main X server installation though.far more efficient than with X11
In theory. The issue is that, at this point in time, the vast majority of software that actually needs this efficiency (read: video games) run on XWayland, which adds a bit of overhead which ultimately causes them to run slightly slower on Wayland compositors compared to X.org. Maybe this will change at some point as devs patch their native games to check for a Wayland compositor by default and the big set of Wayland-support-patches makes its way into wine (and hopefully proton).
X12 actually exists. That said, it never went further than an extremely rough draft and was abandoned at some point, ultimately in favor of Wayland.
I like how the majority of the list is "stuff that doesn't exists on Linux can't be properly used on Linux". Yeah, no fucking shit, Sherlock.
I also like how it's supposed to be about the "average user" and then lists a ton of stuff that's only used in niche applications when put in relation to the entire desktop market.
Additionally:
People that run old software / games because not even those will run properly on Wine;
A good amount of old games won't run properly on Windows anymore, either.
I can't see any of the downvotes that DerisionConsulting mentioned, possibly because I'm on kbin, but I can absolutely understand why people would downvote this completely braindead article that doesn't mention a lot of the actual issues (i.e. hardware compatibility on laptops, friction from the slow transition from X to Wayland, inconsistent user interfaces, updates breaking stuff on some distros, ...).
This is generally good advice. Would you run the program without a sandbox? No? Then you probably shouldn't run it inside a sandbox either.
You can never be sure that the program isn't using a flaw in the sandbox to break out or is just piggybacking onto a whitelisted action that is required for the program's basic functionality.
And if some program requires r/w for your entire home directory and network access then you might as well not use a sandbox in the first place because it can already do everything useful that it needs to do.
If you have mouse acceleration on KDE when selecting the "flat" profile then
Bitte sag mir, dass das durch den Fotoladen gegangen ist.
Und dann sag mir, dass du nicht lügst.
Ironischerweise besser für die Umwelt.
On Steam the system requirements are very clear about this: "SSD Required".
Hätten sie mal lieber in Der Gerät investiert.
Even disregarding the trust issues with Flatpak packages made by random people: Packages often contain versions of some libraries in order to not depend on the distro's. If there are security vulnerabilities in a library then the distro maintainers usually fix it very quickly (if not go find a better distro) and it's fixed for all packages on your system that depend on it. But this doesn't apply to Flatpak where the package providers have to update the libraries in their own package - and the track record isn't great. Sandboxing doesn't help if that vulnerability leads to wiping your home directory.
In the vast overwhelming amount of cases tooltips show additional information that you cannot see from clicking on something or provide an explanation to an option that isn't available without scrounging through a manual. None of those apply here.