This type of grass is always greener answer is why the Linux desktop experience is so poor. If someone follows that advice they may fix one issue they have but in return they get a whole new set of problems to discover and troubleshoot or run away from.

I used Gentoo for a very long time (2005-ish to 2009 or so) and tried Arch, too, both back then (after I, uh, toasted a power supply compiling packages for five days straight) and more recently, about a year ago. It's a very good approach, but far too high-maintenance for my taste. During my (latest) short stint with Arch, I became a walking bug tracker. Stick to Adwaita because everything else breaks, don't do that in a KDE app because it crashes, try to reboot my computer only to find out it's stuck in a loop because some process can't notify some other process through D-Bus...

There's a bunch of stuff that doesn't work on Debian, either, but at least it's the same stuff for about a year or so.

Nowadays I get to write Linux software at work so I get all the bleeding-edge stuff there, and dealing with the latest and greatest breakage is part of my everyday job. I have no desire to do it at home, too.

Edit: plus, to put it bluntly, it's really no longer fun. When I said goodbye to Windows, back in nineteen-ninety-something, I did it to get away from the mind-boggling complexity and uncustomizable blackbox blurb on my hard drive.

Nowadays, it's an order of magnitude more complex; some of it is unwarranted and much of it just isn't reliable. Windows' and OS X's isn't, either, but at least it's nicely tucked away behind an interface that works, so you're not exposed to the crap underneath. I spend a lot more time wrestling with my computer than I'd like to.

I can mostly navigate through this whole maze of thisandthatkit and systemd-everything, largely because I'm exposed to it for eight hours a day, whether I want it or not, and have seen it being developed. But I don't think it's sustainable, and I have a feeling I'm going to call it quits one day.