Wednesday, December 14, 2005

Gnome vs. KDE

The never-ending "Gnome vs. KDE" battle flared up again yesterday when Linus Torvalds stated a preference for KDE.

Of course, it was immediately put on Slashdot, so, as Linus once put it, there was a "big public wanking session" about it. There was a lot of misinterpretation very early on, but the actual thrust of his argument, as far as I could tell, was that Gnome has an unfortunate tendency to remove functionality completely in the name of making the interface easier, which of course just leads to a crippled interface. Hence his preference for KDE over Gnome.

I have to say, I've always been puzzled by Gnome. I couldn't see quite where it fit in. If a user wants a lightweight, bloat-free desktop, there are dozens of lightweight WMs that will work better for them than Gnome. If they want a Windows-style, the-GUI-is-everything desktop, KDE is far more impressive. Gnome seemed to have no real niche. I didn't really care enough about the subject to find out any more, but yesterday I found out what Gnome aims to do.

WMs are lightweight and highly customizeable, but you tend to need to configure them yourself to make them useful. KDE can do just about everything out-of-the-box but it's a complex, resource-hungry beast: An out-of-the-box KDE has dozens of items in the menu, and I don't know how many screens of configuration options.

The design philosophy of Gnome appears to be to create a desktop that works out of the box, but without bloating it with lots of confusing functionality. A simple, elegant interface that a total newbie can comfortably use right away, no configuration needed or really even desired.

Now, that's a very, very difficult task. I won't say it's impossibly difficult, but it's outside the reach of most people. It's no surprise that it hasn't achieved it yet, and not unexpected that there's a perception, right or wrong, that there's a tendency to simplify the interface by simply removing functionality instead of making that functionality simple & intuitive. A GUI with the stated goal of removing customizability is at odds with just about every other *nix GUI I know of , so even though it's being removed for the perfectly acceptable reason that they aim to remove the need for it, they've chosen a tough path to follow.

So it seemed an opportune time to mention my experiences with Linux GUIs.

When I was trying to get Lou to switch to Linux, I gave her Ubuntu - Gnome-based. I was disappointed to see that the theme was unchanged from a few years ago when I had Gnome installed as part of Slackware. I know it's shallow, but first impressions count, and the default Gnome theme just looks naff to me. Uninspired icons on a plain grey background. Maybe they aimed for a conservative appearance to appeal to corporate users, I don't know. But a Gnome desktop just doesn't shout out "I'm wonderful, use me!". It's more of a resigned sigh. It's nowhere near as enticing as a default KDE appearance.

If it made up for that by being simple but highly functional, which is the whole aim, it could probably be forgiven. But it wasn't. Simple, yes. But it really didn't do much. Certainly printing was a no-go without doing a CUPS configuration thing. I believe Gnome's lack of printing support was the reason KDE was chosen in a number of corporate environment, in fact. . .

So we switched to Kubuntu, the KDE-based version, to give that a try. Everything worked. Knowing just what a pain setting up CUPS can be, I was genuinely impressed that KDE simply detected her printer & set it up for her. It was slower to load, certainly, but it worked fine when it was up & running, and at the end of the day, it actually did stuff.

So when she switched to FreeBSD, she didn't even bother with Gnome: KDE all the way. Just as well, in many ways. In Linux, you use Alsa for sound. I know how to set that up. I have no idea what BSD uses, or how to set it up. I didn't need to find out, as KDE did it for her. It's a really impressive piece of work, KDE.

I hate it, but it is impressive. :o)

Why do I hate it? The bloat. The sheer amount of crap that fills every menu. The fact you have to do everything the KDE way, via KDE, instead of just doing it your own way. In the same way that an MS Windows machine is always an MS machine, KDE is always KDE. It gets in the way of itself.

Hence the whole "Gnome vs. KDE" has no place in my life: The answer is always "Neither, hate them both." Even the short periods when I use Knoppix grate on my nerves.

But if anybody asks "What desktop should I use?" my answer is "If you need to ask, use KDE." If you don't know enough to pick a GUI, you probably don't know much else about Linux. KDE will get you up & running in spite of it. Gnome won't.

Not yet, anyway. Hopefully they will in future. After all, choice is one of Linux's biggest advantages. If Gnome didn't exist, it would have to be created. There always has to be "Something vs. KDE."

2 Comments:

hari said...

I agree that Gnome really doesn't have a "niche" as such. It's an odd misfit in a desktop world that is highly polarized between the heavyweight KDE and the "lightweight" DEs. In fact, I think whatever niche Gnome used to have is fast being evaporated by the likes of Xfce.

Now regarding your observations on KDE. About its bloat and complexity. I disagree. It *is* extremely functional, but you can really trim it down to the size you want. By default, it is functional and gets the job done as you mentioned and that's a big plus.

Getting in the way and doing things the "KDE" way? I wouldn't say that. You can almost always bypass KDE by using GTK apps within KDE. You can do direct configuration of devices without bothering about KDE's device managers. In fact, I would give KDE a thumbs up purely because it offers alternatives without forcing the user only to choose KDE. It's after all, only a desktop environment: not a full fledged OS like Windows, so comparing it to Windows is not really on.

I always keep coming back to KDE in spite of other desktops because I know KDE. I am comfortable and it works the way I want it.

Ultimately as I have observed before, choice is the spice of desktop Linux!

3:50 PM  
Dominic said...

It's true that you can trim KDE down. But then, you can actually trim Windows down if you put the effort in. Even to the point of not having IE installed! A friend of mine has a working Windows live CD that's under 50MB, in fact.
But being able to reduce a large complex thing is not the same as having a small and simple thing. "inside every fat person is a thin person dying for cholcolate" ;o)

And my "KDE way" complaint isn't about having to use only QT apps. It's partly about things like: if I want to change KDE's appearance, I have to open the KDE menu to start the KDE control center and use KDE's help system if I have a problem. . .

But more especially, it's about: If I want to put the toolbar on the side of a window instead of the top, have four buttons at the top of the toolbar and three at the bottom, and have no taskbars but just have the main menu pop up at a mouse-click. . . Well, I'd not find it easy to set that behaviour up in KDE. KDE is set to work a certain way: With menus accessed via taskbars and window decorations on top.

Certainly, with enough time & effort, you can change this behaviour. But that's just it: It *is* time and effort. It's not a simple change. FVWM might seem complex, but I could shunt my toolbar to the side of my windows with about ten seconds use of Vim, and switch a menu from a taskbar to a mouse-click binding in about the same length of time.

In the same way that MS Windows will always look like MS Windows unless you're a dedicated hacker, KDE will always look like KDE. You can fiddle with icon themes and colours, but you can't change fundamental aspects without putting in some serious work.

Of course, most people don't care about such functionality. But I do, hence KDE is just not suitable for me.

Vive le difference! :o)

5:25 PM  

Post a Comment

<< Home