Looks alright to me.

Not a specialist, but I suppose it has to do with having different configurations for different top level folder. In Unix-like systems, every top level folder have a different purpose, and what works for the root may not for /tmp, /swap, etc.

In those example, no need to snapshot /tmp, as it is a forder whose file are bound to be deleted, and for which being able to restore has no use.
/swap is pretty similar ~~, and is often formated with a dedicated filesystem.~~
/usr often only change during the package manager transactions, so snapshots are often tied to that, while /home may be set to keep daily snapshots.

Pedantic? Say the person that immediately assume anyone with a different opinion than his is a morron and did not read his previous message ?

Here is some gaming benchmark. It is from 2022, sure, but is still relevant today to illustrate that gaming performance on Linux isn't as easy as being the "same software with different configuration".

And I could go on with other games, which had different results.

There are many variables that can affect those performance. Obviously, the Kernel, Driver and Mesa version has a big influence, but so have some less obvious causes like the filesystem used, the compiler options used, or even the compiler itself. That's why those performances can vary so much in benchmarks.

Phoronix many benchmarks proves the opposite. There is differences, even at the same Mesa/Kernel version.
The difference between an hyper optimized distro, like Clear Linux (optimized for Intel CPUs), and more general ones (Ubuntu, Fedora) can be huge.
Even between those general purposes distro, the technology choices (filesystem, scheduler, etc.) can make a considerable difference in some games/workloads.

Too bad it is nVidia only.

For overclocking you have LACT.

You can also change this behavior in libzypp configuration file, if I recall well.

I have used TW for years, and never got bothered by a breaking change for more than a day. And that only happened twice.

The only thing that keeps bothering me with Opensuse is their obsession with asking for a root password (and not for yours if you are an administrator, I mean the root user password) for every damn thing. Even installing a fucking user Flatpak requires a fucking root password !

I saw it, selected the loosest one, still way too overbearing.

I didt try Debian tbh.

But what do you mean by not configuring root? Not configuring the root user password?

In my case I already tried to contribute to OpenSUSE, but to keep interest I want to be able to daily drive it. But for now there is a significant number of blockers that prevent me from doing this.

First, the unconfigured default state where Root and only him can do privilegied talks. OpenSUSE is the only distro, to my knowledge, to leave Sudo unconfigured. This result in asking for root password for literally any task. And even once Sudo had been properly configured, Polkit rules are so tight you need to type Root password for many thing more user friendly distroes like Fedora and Ubuntu execute without asking for any password.

And the bloat of the packages patterns are horrible. The base install comes with multiple softwares that are either usefull to almost no one, or that do the same thing as other does. Like xterm installed alongside Gnome Terminal by default, or tigervnc and Gnome Connexion.

It is horrible enough for me to have started my own repositories on OBS to be able to remove some of this bloat by building my own preconfigured package and less bloated patters.

I can validate that. Switched my NAS to amd_pstate, went from 2.12 kW.h per day to 1.95 kW.h per day.