The rise of "It just works"
I am not a very technical user. Many decades ago I learned to bumble around the 'nix filesystem in whatever shell Solaris gave us at the time. When RISC OS faded away all I could get cheap was Windows, and ran 98SE well into the new millennium. Then the Linux desktop became a thing. RedHat taught me to hate KDE, SuSe YAST, Ubuntu Unity, etc. Debian+GNOME proved the first workstation since the RISC PC that "just worked" for me and, apart from odd forays into Mint and suchlike, I stuck with it until SystemD stuck in my throat and I switched to Devuan. GNOME2 was the first GUI I felt comfortable with after RISC OS, but GNOME3 was so execrable and, frankly, Unity not much better, that I switched to MATE. Being also uncomfortable with vertical taskbars, this "feature" is not a problem to me.
I bump into other Linux users now and then, almost all are in the "it just works" category and fear the shell. They don't participate in the shouting matches ("why war over vi and EMACS, surely a decent text processor is a decent text processor? I just use gedit [or whatever]" "What is SystemD?") Se we seldom see them in the geek haunts, and end up with a false idea of what is "popular" on Linux.
But I do admire Liam's courage in sticking to the subject here and coming back for more. Icon for you, Sir.
And I want to add one more argument to the mix. In Unix/Linux we have always liked our apps to do only one thing but to do it well. This does not always work well; The Hurd is slow, getting init, audio or remote desking to fly can be a pain. OTOH the all-in-one mega-pack destroys things like choice, reliability and maintainability; the user loses control. SystemD, pulseaudio and Wayland bring much heat and hate in their wake. The Linux kernel seeks a middle way, being modular in construction. There is a core functionality, which marks it out as Linux, but most of it comes in modules which can be integrated or not, in various ways according to need. Why do we not take the same approach with perceived monstrosities like SystemD, pulseaudio and Wayland? We have many forks, but each ploughs its own furrow. They should do what Linus does with his kernel; collaborate on a core service, identify the interface architecture to optional functions, and then let the ecology get on with it.
That way, some like-minded geek somewhere will put together a distro which "just works" for you.