Why Was the GNOME Project Founded in 1997?

The GNOME project was founded in August 1997 by Miguel de Icaza and Federico Mena Quintero primarily in response to software licensing concerns surrounding the KDE desktop environment and its underlying Qt toolkit. While KDE provided an intuitive graphical desktop for Unix-like systems, Qt was distributed under a proprietary license that restricted commercial redistribution and modification. To safeguard the principles of free and open-source software, the founders created the GNU Network Object Model Environment (GNOME) as a completely free alternative built on unencumbered libraries.

The Rise of KDE and the Qt Dilemma

In late 1996, Matthias Ettrich initiated the Kool Desktop Environment (KDE) to deliver a unified, user-friendly desktop experience for Unix and Linux workstations. At the time, existing graphical interfaces were fragmented, complex, and unapproachable for average users. KDE quickly gained popularity and filled a critical usability gap in the growing Linux ecosystem.

However, KDE relied on the Qt GUI toolkit, developed by the Norwegian company Trolltech (then Quo Vadis). Qt was governed by the FreeQt license and later the Q Public License (QPL). Under these terms, the source code was viewable and free for non-commercial software development, but proprietary for commercial applications. Furthermore, users could not distribute modified versions of the library freely.

This arrangement conflicted with the core philosophy of the Free Software Foundation (FSF) and the GNU General Public License (GPL). Because KDE code was licensed under the GPL while linking against non-free Qt libraries, it created a legal and ethical dilemma: distributing the combined software violated the terms of the GPL itself. Free software advocates feared that the entire Linux desktop could become dependent on proprietary technology controlled by a single vendor.

The August 1997 Announcement

On August 15, 1997, Miguel de Icaza posted a historic announcement to the comp.os.linux.announce newsgroup:

"We are going to develop a free and complete set of user friendly applications and desktop tools, similar to CDE and KDE but based entirely on free software."

Icaza and Federico Mena Quintero named the effort the GNU Network Object Model Environment, abbreviated as GNOME. The initiative received immediate backing from the GNU Project and Richard Stallman, who recognized the urgency of providing a fully free desktop environment before KDE’s proprietary foundation became permanently entrenched.

Technical Foundation and Strategic Decisions

Rather than reinventing every component from scratch, the GNOME founders built upon existing open-source components that carried permissive or copyleft licenses.

• GTK+ (GIMP Toolkit): Instead of using Qt, GNOME adopted GTK+, a library originally designed by Peter Mattis and Spencer Kimball for the GNU Image Manipulation Program. GTK+ was licensed under the GNU Lesser General Public License (LGPL), allowing both free and proprietary software developers to create applications without licensing conflicts.
• Component Architecture: Inspired by Microsoft's Component Object Model (COM) and Object Linking and Embedding (OLE), GNOME sought to create a reusable component architecture using the Common Object Request Broker Architecture (CORBA) standard via a framework called Bonobo.
• Language Agnosticism: GNOME was deliberately designed to support multiple programming languages, including C, C++, Python, and Perl, lowering the barrier to entry for prospective contributors.

Industry Impact and Resolution

The emergence of GNOME applied significant competitive pressure on Trolltech. To resolve the licensing controversy and preserve KDE's viability within standard Linux distributions, Trolltech relicensed Qt under the QPL in 1998 and ultimately dual-licensed it under the GNU GPL in September 2000.

Although the original licensing catalyst was resolved, GNOME had already gathered immense developer momentum, institutional backing from companies like Red Hat and Sun Microsystems, and a distinct design philosophy centered on accessibility and simplicity. The project matured into one of the default desktop environments across modern Linux systems.