A few weeks ago, Jack Wallen published a comparison of recent GNOME and KDE releases in which he claims that the desktop flame wars in GNU/Linux were about to reignite, and that KDE would emerge as the loser. It was not the most technically accurate of articles, and the claim of renewed desktop wars was news to me; in the mail forums for Debian, Fedora, and Ubuntu, the uproar over the changes in KDE 4 is over, except for a few die-hards who are sounding increasingly crankish.
The claim sounds like one of those overly dramatic statements that some journalists make in the hopes of creating controversy and increasing page hits.
Still, Wallen's blog entry and various recent episodes in my own quest for a perfect desktop got me thinking: How do GNOME and KDE compare in spring 2009?
The question has never been a easy one to answer. The last time I tried to answer the question, I wimped out and said that the answer depended on what you were looking for.
In many ways, that answer still holds, even if it's not dramatic or very satisfying. Both GNOME and KDE are mature, fully-featured desktops, and the two projects cooperate on common interface standards via freedesktops.org, so the differences between them are often minor. At best, the answer tends to be a careful tallying of the balance sheet, with the victory going to one side or the other on the basis of points rather than any knockout blow.
More importantly, the most obvious difference between the two major free desktops is philosophical. When KDE 4.0 was released, the project showed itself willing to make revolutionary changes, breaking with the past to such an extent that even backwards compatibility was not guaranteed.
User complaints, often loud and abusive, did not so much shift KDE from the direction it was heading as encourage the creation of new mechanisms for gathering user feedback and a reconsideration of how subsequent releases were managed. This reaction might seem high-handed, especially by the egalitarian standards of free and open source software. But, over time, the project's determination seems to be outlasting the complaints about change.
By contrast, as Ryan Paul points out, GNOME has backed away from radical changes in favor of incremental changes. Instead of planning for a 3.0 release, GNOME is opting for a gradual, piece by piece updating that will culminate in a 2.30 release. The change in version numbers is significant: It indicates that, unlike with the KDE 4 series, there will be no major break with past releases. This philosophy was obvious long before it became official last summer, and has the obvious advantage of not alienating users.
These differences are not absolute, of course. For instance, the last two releases of KDE suggest that the project is content to implement usability in an incremental fashion. Similarly, when GNOME-centered distros like Fedora introduced PulseAudio last year, the uproar was a small echo of the complaints over KDE 4.0.
But, in general, the difference in approaches is obvious, and which you prefer says more about your own philosophy than about the advantages or disadvantages of either. With the majority of people tending toward conservatism, many are going to prefer GNOME's gradualism, but, for others, the radical innovation of KDE is always going to hold more appeal. In expressing their own preferences, people are apt to overlook that they are not saying anything objective -- that is, not referring to anything outside themselves. So long as the discussion stays on this level, it can never hope to produce useful answers.
For this reason, I prefer to make the question more specific -- not which desktop is subjectively better, but which developmental approach is likely to be most successful in the next few years?
With this reframing, a more useful answer is possible -- and I would say that, despite some necessary qualifications, the advantage lies with KDE.
I base this statement largely on a single observation. Before KDE 4's release, both KDE and GNOME were struggling under the weight of legacy code and practice. As Andy Wingo wrote last year about GNOME, both desktops were in "a state of decadence."
One of the ways around the issues of security and control that make some businesses wary of cloud computing is to build a private cloud -- one that remains within the corporate firewall and is wholly controlled internally. Private clouds also increase the agility of IT an organization's IT infrastructure and make it easier to roll out new technology projects. Download this eBook to get the facts behind the private cloud and learn how your organization can get started.