After having a lot of sysvinit experience, the transition to setting up my own systemd services has been brutal. What finally clicked for me was that I had this habit of building mini-services based on shellscripts; and systemd goes out of its way to deliberately break those: it wants a single stable process to monitor; and if it sniffs out that you are doing some sketchy things that forks in ways it disapproves of, it is going to shut the whole thing down.
On the topic of things to never forgive Redhat about, aren’t there other things that are more pressing? Like, inventing a whole scheme to circumvent the idea of the GPL license via service contract blackmail?
I couldn’t agree more. If there only was a somewhat user-friendly setting that allowed the oom killer to be far more aggressive, killing or freezing processes as soon as their memory use starts to affect system responsiveness, and just tell me this is what has happened.
That’s On Me, I Set the Bar Too Low 
Ubuntu user here. Swapped away from Debian in its early days when Ubuntu made a real effort to stay current with the desktop environment (even coordinating their releases after GNOME), and back then it mattered. Nowadays my few attempts at other distros suggest that the hardware driver situation (especially proprietary) seems better on Ubuntu, for example to get everything working on fairly new laptops.
There are of course other things I’m less happy about. The snap installs via apt drives me crazy; not that I necessarily hate the technology, but sometimes I need a non-containeraized browser (for example to run inside another container), so I need to be allowed to choose what is being installed.
Are you using x11 or Wayland? Is anyone running Wayland with NVIDIA drivers? Everything works well in x11, but I’m getting bad flicker in Wayland. When trying to track it down I was led down a rabbit hole suggesting there is some protocol mismatch between what the NVIDIA drivers implement and what Wayland expects.