Jump to content

Comparison of X Window System desktop environments

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 175.139.212.239 (talk) at 00:48, 20 April 2016 (Technical elements of a desktop environment). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

A desktop environment is a collection of software designed to give functionality and a certain look and feel to an operating system.

This article applies to operating systems which are capable of running the X Window System, mostly Unix and Unix-like operating systems such as Linux, Minix, Solaris, FreeBSD, and Mac OS X.[1] Microsoft Windows is incapable of natively running X applications; however, third-party X servers like Cygwin/X, Exceed, or Xming are available.[2][3]

Technical elements of a desktop environment

A desktop environment (DE) can be broken up into several components that function independently and interact with one another to provide the look and feel and functionality of the desktop environment. A fundamental part of a DE is the window manager or WM. A window manager creates a certain way for application windows to present themselves to the user. It manages the various application windows, keeping track of which ones are open and providing features to switch between them. Another important element of a DE is the file manager. This application manages files/ folders and presents them in a way that the user finds convenient. It provides file operations like viewing, copying or moving, changing permissions and deleting. DEs usually provide utilities to set wallpapers and screensavers, display icons on the desktop, and perform some administrative tasks. They may optionally include word processors, CD/DVD writing applications, web browsers and e-mail clients.

There are some exceptions: Window managers like Fluxbox, wmii and Ratpoison operate independently of a desktop environment and were written with this objective in mind. Additional hand-picked applications add functionality such as a panel and volume management which gives them some of the qualities of a full DE. This contrasts the behaviour of WMs like Metacity and KWin which were not written with the objective of operating independently of a DE.

KDE Software Compilation and GNOME are written almost completely on special software libraries Qt and GTK+ respectively.[4] This usually means that virtually every component of the desktop environment including the file manager explicitly depends on that library for its functioning.

KDE file manager Dolphin running under GNOME

Notably, nothing prevents the user from installing any number of software libraries of his/her choice. In practice, software written on major libraries can be run under any desktop environment. Running a package designed for one desktop (which essentially means that it's written using the same libraries as the desktop itself is) within a different desktop can be visually displeasing, as well as incurring the RAM penalty of loading libraries that wouldn't otherwise be required.

Some of the differences which can influence the choice of desktop environment are:

  • Look and feel of the desktop environment. The user will be more comfortable with a certain look and feel that he/she may or may not already be familiar with.
  • Flexibility and configurability of the desktop environment. A sophisticated user might want a highly configurable desktop environment to make the desktop environment work the way he/she wants. A beginning user might just want an easy-to-use environment to which he/she will adjust.
  • Personal preferences for choice of software, which has two aspects:
    • Each desktop environment comes packaged with various default software and various "ways things are done" under that desktop. A casual user might like a highly integrated graphical interface to change various settings while a more experienced user might prefer to use individual configuration utilities or even CLI tools.
    • Desktops are also often closely tied into various major functional components of the desktop manager (example: file manager, browser, word processor); whilst "mix and match" is possible, it is generally pleasing to make choices which result in a consistent look and feel of programs under the chosen desktop environment. Making choices based on what software integrates with a chosen desktop environment necessarily limits the weight that can be given to other application features.

Desktop comparison information

Overview

Full environments Shell (semi-environment)
KDE Software Compilation LXQt GNOME MATE Xfce, LXDE and ROX Desktop Étoilé EDE Enlightenment
Main objective[5] Full desktop environment, graphical, easy to use, targeted at everyone. Focus on providing advanced features and configurability. Lightweight desktop environment, modular, portable. Full desktop environment, graphical, easy to use, targeted at everyone. Emphasis on ergonomics and workflow simplification. Forked from GNOME. Emphasis on providing the traditional desktop metaphor eschewed by GNOME 3. Lightweight desktop environment, modular, portable. Advanced graphical libraries, tools and environments
Programming language[6] Mainly C++, as Qt is written in C++ Mainly C, as GTK+ is written in C Objective-C C++ C
Additional library dependencies[7] KDELibs, KDE Frameworks 5 requires window manager libgnome libmate libxfce* for Xfce. libede EFL
Toolkit used[5] Qt GTK+ GNUstep FLTK (previously eFLTK) Elementary (provided by EFL)
Size (base system, X installed)[8] ~210 MB ~20 MB ~180 MB Xfce: ~15 MB, ROX: ~780 KB EDE: ~3 MB DR16: ~3 MB, DR17: ~15MB

Default programs packaged

This table shows basic information on the programs distributed with some desktop environments for the X Window System.

KDE Software Compilation GNOME Mate Xfce LXDE ROX Desktop Étoilé EDE Enlightenment
X window manager KWin Mutter Marco Xfwm4 Openbox OroboROX Azalea edewm Enlightenment
X display manager KDM, SDDM GDM LXDM elma Entrance
File manager Dolphin (Konqueror before SC 4) Files Caja Thunar PCManFM ROX Filer Efiler EFM, Entropy
Widget toolkit Qt
GTK+
GNUstep FLTK (previously eFLTK) Elementary
Terminal emulator Konsole GNOME Terminal MATE Terminal Terminal LXTerminal ROXTerm aterm Terminology
Text editor KWrite (Kate before SC 4) gedit Pluma Mousepad, Leafpad Leafpad Edit TextEdit Eyesight, Ecrire
Video player Dragon Player (Kaffeine before SC 4) Videos Parole lxine mplayer-rox Enna (media center), Eclair
Audio player JuK, Amarok Banshee, Rhythmbox LXMusic MusicBox Melodie Enjoy
CD burners K3b Brasero Xfburn RoxISO
CD ripper K3b, KAudioCreator Sound Juicer Ripper Extrackt
Image viewer Gwenview Eye of GNOME Eye of MATE Ristretto GPicView Picky Eimage Ephoto
Office suite Calligra Suite, KOffice GnomeOffice
Web browser Konqueror Web Midori Eve
E-mail client Kmail Evolution GNUMail
Personal information manager Kontact Contacts
Instant messenger Kopete, KDE Telepathy Empathy Shotgun
Archive manager Ark Archive Manager Engrampa Xarchiver, Squeeze Xarchiver Archive
PDF viewer Okular (KPDF before SC 4) Evince Atril Vindaloo Epdf
IDE KDevelop Anjuta Gorm, ProjectCenter
X session manager ksmserver gnome-session mate-session Xfce4-session LXSession ROX-Session
Widget engine built-in – Plasma (SuperKaramba before SC 4) gDesklets Elementary
Licenses used GPL, LGPL, BSD, others GPL, LGPL GPL, LGPL GPL, LGPL, BSD GPL, LGPL GPL GPL, BSD GPL, LGPL BSD, LGPL
KDE Software Compilation GNOME MATE Xfce LXDE ROX Desktop Étoilé EDE Enlightenment

Note that Razor-qt has become LXQt, a port of LXDE to the Qt framework.

Comparison of ease of use and stability

GNOME's graphical file manager Files (Nautilus) is intended to be very easy to use and has many features.[9] KDE's file manager Dolphin is described as focused on usability.[10] Prior to KDE version 4, the KDE project's standard file manager was Konqueror, which was also designed for ease of use.

Both GNOME and KDE come with many graphical configuration tools, reducing the need to manually edit configuration files for new users. They have extensive bundled software such as graphical menu editors, text editors, audio players, and software for doing administrative work. All applications installed in most distributions are automatically added to the GNOME and KDE menus. No major configuration changes are necessary to begin working. However, by using graphical tools, the extent to which the desktops can be configured is determined by the power provided by those tools.


Compatibility and interoperability issues

Some desktop environments and window managers claim that they support applications made for other desktop environments explicitly. For example, Fluxbox states KDE support in its feature list.[11] Using software made specifically for the desktop environment in use or window manager agnostic software is a way to avoid issues. For software developers, the Portland Project has released a set of common interfaces that allows applications to integrate across many desktop environments.[12]

System resources utilization

A 2011 test by Phoronix with the default installation of Ubuntu 10.04 showed that LXDE 0.5's memory utilization was lower than that of Xfce 4.6, which in turn was lower than that of GNOME 2.29, with KDE 4.4 using the most RAM compared to the aforementioned desktops.[13][14]

See also

References

  1. ^ XFree86 Official Website line 5
  2. ^ Cygwin/X website
  3. ^ Xming project homepage on SourceForge
  4. ^ Official websites of GNOME and KDE
  5. ^ a b Excerpts from official websites
  6. ^ Analysis of source code tells the programming language used
  7. ^ Dependency list for metapackages
  8. ^ Reported apt-get installation size on a very basic Debian system with X
  9. ^ Official Nautilus screenshots page
  10. ^ [1]
  11. ^ Fluxbox official website line 15
  12. ^ Linux leaps toward KDE/GNOME compatibility
  13. ^ Larabel, Michael. "Phoronix: Power & Memory Usage Of GNOME, KDE, LXDE & Xfce". Phoronix. Retrieved 30 July 2011.
  14. ^ RAM use of LXDE vs Xfce in Porteus again confirms that LXDE is about 1/2 of that of Xfce