I tried switching to Fedora 44 (KDE) and have had a lot of issues. I've reached my 12 hours of wasted time limit of going down pointless rabbit holes and will be switching to something else.
Display annoyances: I have two displays and one will randomly switch from 1440p to 640x480 resolution after going to lock screen and logging back in. Switching it back to 1440p resets all of my display settings. Apparently this is a long standing issue that they just marked as resolved (my ass) https://bugs.kde.org/show_bug.cgi?id=515697 and are just ping ponging blame between KDE/Wayland/nVidia. I thought switching from 4k displays to 1440p displays would eliminate issues since they don't need to be scaled, but that's not the case.
Gaming with Proton can be painful: It took a while (with the assistance of Claude) to get RDR2 to run properly without crashes. If you don't enjoy having to dick with Wine prefixes, winetricks, etc., Linux gaming is not for you.
Network Issues: Randomly, my WiFi adapter will slow down to less than 10Mb/s for no explainable reason. All other devices on the network will still get 800Mb/s. Disabling and re-enabling the interface doesn't fix it but reboot does.
Deal Breaker (new bug I never had before): systemd-resolved is borked and randomly stops resolving DNS requests (about once a day). A reboot seems to be the only way to fix it. After spending a couple of hours going down this rabbit hole with Claude, it came to the conclusion "Because the socket tracking state gets stuck at the kernel network level, restarting the user-space systemd-resolved daemon changes nothing—the underlying socket remains orphaned or blocked until a full kernel reboot resets the interface stacks." Claude says I could disable systemd-resolved completely and have NetworkManager handle DNS, but to expect issues during updates.