When GNOME began in 1997, the project had a clear purpose. At the time, there was no other free desktop, since KDE relied on the then-proprietary Qt toolkit. But today, looking at the mounting evidence of problems within the project and the denial of many project members, I have to ask: Does free software still need GNOME? Or has it outlived its usefulness?
The fact that such questions seem reasonable today is a bizarre reversal. Years ago, KDE became unquestionably free software. Yet the rivalry between GNOME and KDE, sometimes friendly, sometimes fiery, has long driven the development of the desktop to the benefit of all. The need for cross-compatibility, to say nothing of the hopes of equaling or surpassing each other, improved both desktop environments.
But now? Desktop-oriented users can choose not only from GNOME and KDE, but also Unity, Xfce, Mate, Cinnamon, LXDE and half a dozen others, all offering a convenient, customizable interface. With so many choices, at first you might imagine that the decline of any one alternative doesn't matter much, no matter how distinguished its history.
However, in GNOME's case, such a conclusion would be superficial. While a permanent decline in the relevance of GNOME would not be fatal to the larger free software community, it would be crippling in several ways -- a loss of developers, applications, and resources from which the community could take several years to recover.
One reason to be concerned about GNOME's future is that for years it has been a major free software project. Over the years, it has attracted a community of active developers -- perhaps 40, if you accept Benjamin Otte's estimate, which probably means another 80-120 semi-regular contributors. If GNOME continues to decline, many of those developers could be lost to free software.
According to the GNOME Census carried out by Neary Consulting, about one third of GNOME developers are employed by corporations to work on GNOME.
In the short run, most of these developers will probably continue to work on GNOME. Some, however, might switch jobs if GNOME no longer seems relevant. Others might find that their corporate sponsors withdrawing or lessening support, and lack replacement sponsors.
For instance, if, as Otte suggests, core GNOME development is being funded largely by Red Hat, what happens if Red Hat decides GNOME is no longer worth attention? In such a case, formerly funded developers might continue to contribute as volunteers, but become less active because of the need to balance GNOME involvement with earning a living.
Similarly, the two-thirds of GNOME developers who volunteer might also drift away. While many developers write code for more than one application, the GNOME Census suggests that most of those applications are within the GNOME project -- presumably where they are most comfortable. Some would probably drop out rather than find a new community. Others, given the traditional rivalries, might not care to contribute to KDE or any other desktop environment.
I know of no study that records how contributors act when a free software project ceases to exist. However, a continued decline in GNOME's fortunes might easily mean a loss of dozens of experienced developers to both GNOME in particular and free software in general. In fact, that loss may already be happening, if you believe Otte.
One of the main advantages of a desktop is that it allows applications to share resources. For instance, instead of including its own printer driver, an application can call on the desktop's printing sub-system.
But when the supporting desktop is no longer developed, its dependent applications are orphaned. For a while, the applications can continue to function using old libraries and resources. Perhaps new functionality and dependencies are added to packages, increasing their size. But sooner or later, unless a great deal of rewriting occurs, the applications became obsolete.
Yes, the code is still available, since it is free-licensed. Yet if the eco-system that supports the code no longer exists, it must be re-created, forcing developers to look backward rather than ahead.
Ironically, we have already seen a parallel situation in GNOME 3's dropping of most panel applets -- a perfectly good tradition that many users relied on for everyday activity. In response, Linux Mint restored applets in Mate's and Cinnamon's re-creations of GNOME 2, satisfying users at the expense of slowing innovation.
Although these developments may have been necessary, it's sobering to think that the most noteworthy developments this year on the free desktop have been revivals of a desktop first released a decade ago. Imagine a similar situation on a larger scale, and you have some idea of what the continued decline of GNOME might mean.
The consequences would be particularly severe because GNOME is not only one of the two largest eco-systems of applications in free software, but also one of the most distinctively designed.
Applications like Brasero, Evolution, Rhythmbox, and Shotwell all share a common philosophy embodied in GNOME's Human Interface Guidelines. This philosophy can be summarized as interfaces designed for the most common use-cases, and the elimination of anything else.
Although this design is not for everyone (I don't care for it myself), many prefer it, and probably beginners find it easy to navigate. If nothing else, GNOME's minimalism is the logical counterpoint to KDE's “completist” approach, which, while favored by experienced users, can often be overwhelming and full of irrelevances for others. Having the two extremes as an example can only be a benefit in a community that still doesn't think about usability as often as it should.
When first Ubuntu, then Linux Mint, overtook Debian in popularity, the distribution's role began to change. Instead of being the desktop of everybody's choice, it became a resource center for other distributions. In some ways, Debian became less obvious, but, if anything, its influence increased, with the result that seventy-seven percent of all active distributions are based directly or indirectly upon it.
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.