eWeek Reviews Gnome 2.8 And KDE 3.3

prostoalex writes "eWeek Labs reviewed the latest editions of GNOME and KDE desktop environments, and for all the criteria that eWeek uses for evaluating the software products ranked 'good,' while usability, capability and reliability for both products ranked 'excellent.' The online version is missing the screenshots and ranking tables that the printed version has, but eWeek likes Evolution (for mail), Konqueror (for file management), Samba and Kopete. They dislike GConf (still complex and a hassle to use) on GNOME and KMail on KDE."

Comments

Screenshots

[Anonymous Coward]

Here are some GNOME and KDE screenshots.

So essentially you are looking for XFCE.

[reality-bytes]

You'd be looking for XFCE then.

XFCE is a powerful but lightweight UI for both older systems and 'power-user' implementations.

Both Gnome and KDE lead the way for moder UI implementations on *nixes and as such require modern hardware to go with them (in general).

Having said that, I've just installed KDE on a second user 1.7GHz Celeron M laptop with a piddling (by modern standards) 128MB ram and it positively flies! - No complaints here.

Re:no for both

[Coryoth]

what linux needs is a desktop environment that uses a fast toolkit, and does what is needed without the extra bells and whistles.

For light desktops that aren't just pure IceWM or *box window management your best options are XFCE (which uses GTK+, but is still surprsingly light and fast), and E17 (if and when it eventually arrives) which uses pretty much all its own technology (of which there is a lot, and its all quite impressive).

Realistically E17 is stacking up to the "other" desktop given how much functionality the E Foundation Libraries offer. I'm not trying to dis IceWM or Fluxbox here, but realistically those are mostly Window Managers, while the new E is looking to have more of the "core libraries" approach of GNOME and KDE, providing its own widget toolkit and what have you. We're still to see whether people will actually pick it up and develop with it...

Finally you've got WindowMaker, which is a very nice window manager and integrates in with GNUStep to provide your widget toolkits and other core libraries. The downside here is that while Window Maker is great, the amount of developer uptake for GNUStep has been fairly limited, so you won't exactly see a lot of GNUStep apps.

There are some good options though, so don't go complaining too much.

Jedidiah.

Re:I like both

[dmaxwell]

KDE moved away from CORBA quite some time ago. Apparently, it proved to be a hairball that made things more complicated than they needed to be. KDE uses "KParts" for object embedding.

Re:what's wrong with Kmail?

[Flower]

The spam filtering issue they discuss isn't a minor UI "niggle."

Re:I like both

[nathanh]

I'll agree that there are probably more layers than you'd ideally want for a desktop (eg: KDE -> Corba -> Underlying KDE stuff -> QT -> Xlib -> X11 client -> X11 protocol -> X server) but it's not horrible and most of the problem is caused by X11's design, which is very much a concept of layers on layers.

Yes, well it would be bloated when you insert mythical layers. KDE doesn't use Corba and Xlib doesn't layer on top of an X11 client; the KDE application *is* the X11 client. And calling the X11 protocol a "layer" is a bit of a stretch.

Amended diagram: KDE -> Kparts/Klibs -> Qt -> Xlib -> Xserver.

KMail and HTML

[anduril1]

Quoth the review:

Another thing that annoyed us about KDE's mail handling was the way it dealt with HTML messages. By default, every HTML message appears in source view, with a security warning and a link to render the HTML for viewing. We could opt instead to have all HTML messages render by default, but we'd prefer that Kontact provide the option of rendering the message in a "sanitized" form-one that doesn't fetch remote images or objects. Evolution and Thunderbird work this way by default.

KMail (and therefore Kontact) does provide "sanitized" HTML mail support. The KMail docs claim that sanitized is the default, but it is an easy change regardless. The check box is located in: Configure KMail -> Security -> "Allow messages to load external references from the Internet". It seems they didn't look too hard for the option that is default anyway.

As far as the warnings before rendering HTML messages, this is just a question of how paranoid you'd like to be (or, how important the integrity of you system is). HTML parsers/renderers are very complex software, and therefore they may have bugs. Look to the recent JPEG exploits for bad bugs in seemingly innocent software. If there were a bug found in the HTML renderer used by your mailreader, reading email messages might present a threat to the security and integrity of your computer.

Like the documentation in KMail says "Displaying the HTML part makes the message look better, but at the same time increases the risk of security holes being exploited"