The GNOME 2 Zombie: Page 3

Disappointment with GNOME 3 has users pining for GNOME 2. But it's not always wise to resurrect the dead.


You Can't Detect What You Can't See: Illuminating the Entire Kill Chain

(Page 3 of 3)

You may remember Linus Torvald's famous complaint seven years ago:

This "users are idiots, and are confused by functionality" mentality of Gnome is a disease. If you think your users are idiots, only idiots will use it. I don't use Gnome, because in striving to be simple, it has long since reached the point where it simply doesn't do what I need it to do.

Torvalds was complaining that, in the effort to provide streamlined, polished applications, GNOME and many of its core applications were removing functionality from the graphical interface.

Torvalds himself has flip-flopped on his choice of desktop environments several times since making this remark. However, if you compare almost any GNOME core application with its KDE equivalent, his remark is -- if anything -- even truer than when he made it.

Whether you're comparing GNOME's Banshee music player to KDE's Amarok, Brasero to K3B, or Shotwell to digiKam, the tendency is unmistakable. On the one hand, in all of the GNOME applications, at best beginner to intermediate functionality is supported. On the other hand, in all the KDE applications, functionality exists for every level of user, including the advanced.

This tendency might appeal to users who are first learning an application. However, it can quickly become frustrating as users want to do increasingly more complex tasks or if problems emerge. Like zombies trying to cope with the modern world, in such cases, applications designed for GNOME 2 often lack the necessary capacity.

As Dead as John Cleese's Parrot

Such shortcomings tend to be overlooked when people look back at GNOME 2. For many users, GNOME 2 has the advantage of familiarity, and they have long ago learned to overlook such shortcomings -- especially when viewing it through a lens of nostalgia.

Yet the fact remains: GNOME project developers were not merely justifying their wish to do something new when they began working on GNOME 3. GNOME 2 was approaching the end of its natural life span, and keeping it on life support -- let alone keeping it healthy -- would have required more and more work with every passing year.

Increasingly, many parts of GNOME 2 would have had to be removed and replaced with ideas transplanted from other sources.

The only trouble is, developing GNOME 3 has proved as difficult as keeping GNOME 2 on life support. GNOME 3 exaggerates the design philosophy that began in GNOME 2, and introduces questionable assumptions of its own.

Under the circumstances, reacting to GNOME 3 by retreating to GNOME 2 is understandable. However, whether it is advisable is another matter. As Linux Mint's Cinnamon has already started to show, GNOME 2 requires extensive surgery after a year of neglect, and the effort is not trivial.

In the long run, the wiser strategy may have been to let GNOME 2 rot in peace.

Page 3 of 3

Previous Page
1 2 3

Tags: Linux, Linux desktop, Gnome, KDE

0 Comments (click to add your comment)
Comment and Contribute


(Maximum characters: 1200). You have characters left.



IT Management Daily
Don't miss an article. Subscribe to our newsletter below.

By submitting your information, you agree that datamation.com may send you Datamation offers via email, phone and text message, as well as email offers about other products and services that Datamation believes may be of interest to you. Datamation will process your information in accordance with the Quinstreet Privacy Policy.