I don't know who "they" refers to in this case. I'm not aware of anyone touting "Linux" as a user-friendly desktop OS. That's what Ubuntu and its variants try to aim for, but that's just the aim of that particular (relatively new) distribution.
"They" are the advocates, the zealots, the people that insist on flogging what is a basically serviceable server OS with a tacked-on graphical environment and a bunch of software with shoddy UI design as the Cure for All Ills in modern computing and the One True Windows-Slayer.
(As for Ubuntu, it's a prime example of the "user-friendly = idiot-oriented" philosophy in dumbed-down UI, though I have seen worse offenders. But even Ubuntu still has that insane Linux complexity under the surface, just waiting for a chance to break out.)
Somewhere in this thread someone noted that Android was "well regarded" yet later on claimed that Linux was no good due to various desktop / user interface issues. On one hand accepting that Linux is just a kernel and on the other citing Linux is both kernel and userland stuff - depending on which argument it serves most best at the time.
Let me clarify: I acknowledge that the Linux kernel is a distinct entity, separate from the userland. The reason I don't accept this as an argument for Linux-the-OS is because
a kernel is not an OS. It's the core component of an OS, but it isn't one all by itself. Linux-the-kernel may be excellent (though I tend to side with Crumb myself,) but Linux-the-kernel is
not what Linux zealots are pushing. They're pushing Linux-the-OS, which adds to the kernel a userland made up of forty years worth of cruft and kludge that has accumulated in trying to build an OS made for timesharing to terminals on mainframes into a modern desktop OS, with stops on every point in between.
Which is basically the
reason Android is well-regarded: it ditches that forty years of cruft pretty much altogether, and replaces it with something more modern (as they did with Java as the official language, keeping the reasonable language/syntax and ditching the monstrous Java library and bloated runtime.) That's why I don't accept "people like Android, therefore people like Linux": it may use Linux-the-kernel, but it is
not Linux-the-OS.
(And when the best thing you can do to get people to like your OS is to throw out everything but the very core, I think that says something.)
It can't possibly be worse than their old shell, and it certainly is an *improvement*, but to a large extent they have missed the point. There's been *numerous* attempts of doing similar shells with types streams and rich meta-data embedded on the Unix side, and all of them have stranded on a few very important things:
I'm not an advocate for object-oriented shells, but I would note that the failure of them on Unix doesn't necessarily prove much other than that Unix isn't well-suited to an object-oriented approach - which isn't exactly a surprise. (Of course, neither is Windows, so there you go.) It would be more informative to try such things on a system whose architecture incorporates object-oriented philosophy in a meaningful way...
Have you actually *used* those systems you compare X to?
Yes.
Unlike Windows or OS X, no single authority gets to choose what we use. The Gnome project, for example, exists because a bunch of people didn't like what the KDE guys were doing, and built their own thing. XFCE exists because those guys didn't like either Gnome or KDE.
I know that. The fact that multiple organizations independently made a poor choice doesn't make it not a poor choice.
"Worse is better" simply means that delivering 80% now is better than delivering 100% ten years from now. It isn't excuse for not delivering a good product eventually - it is a reason for not overdesigning a system so that you never ship anything until it's obsolete. More should learn from that, given the number of great projects that turn to vapour because people overreach (I'm as guilty as the next one..)
It isn't
supposed to be an excuse for not delivering a good product - but it often
is used as one in spite of that.
Um no, there's a *reason* why most people who have experienced the GIMP hates it with a passion, it's because it opens several windows and they spill out all over the place, not being grouped together in any way. The usual answer from the Linux crown - that's what workspaces are for.
The irony, of course, being that the GIMP will just throw windows in whatever workspace you happen to be in, not just the workspace you launch it in.