Language Selection

English French German Italian Portuguese Spanish

In search of the Linux desktop

Filed under

KDE and GNOME are the mainstream desktop environments for GNU/Linux. There are lightweight options that use fewer resources, such as Xfce or Fluxbox, but new users are more likely to encounter KDE or GNOME, which most closely follow the familiar desktop metaphors common to Windows or Mac.

The historic challenge for the KDE and GNOME developers has been to reproduce the functionality available to users of other operating systems, and a bit more besides. But in recent times the developers have begun to look towards a future that might take the desktop further beyond the accepted conventions.

As the KDE developers have expressed it: "Desktop computing has changed radically in the last 20 years, yet our desktops are essentially the same as they were in 1984. It's time the desktop caught up with us."

The point and click desktop as we know it has been around since monitors had flickering green screens, although the average laptop has disk, RAM and graphics capacity that was undreamt of a few short years ago.

The approach of both GNOME and KDE developers is to find ways of taking full advantage of both the expanding technology and the limited spacial characteristics of the modern computer screen. In doing this they have to satisfy the conflicting demands of users.

The 'interface Nazis'

More in Tux Machines

Today in Techrights

A few thoughts on OpenBSD 5.8

I've been using OpenBSD since way back at release 2.3 in 1998, so I've gone through upgrades that took a fair amount of work due to incompatible changes, like the switch from ipf to pf for host firewalling or the change to ELF binaries. The upgrade from 5.7 to 5.8 was a pretty smooth and easy one, for the most part. The two most painful changes for me were the replacement of sudo with doas and the dropping of support in the rc.conf for the pf_rules variable. While sudo is still available as a package, I like the idea of reducing attack surface with a simpler program, so I made the switch. The two things I miss most about sudo are the ability to authenticate for a period of time and the ability to have a single config file across a whole set of servers. The former I'm just living with, the latter I've adjusted to by having a single config file that has lines commented out depending on which server it's on. I did have one moment of concern about the quality of doas when it incorrectly reported the line number on which I had a syntax error in the config file--fortunately, this was just a failure to increment the line count on continuation lines (ending with a "\") which is fixed in the -current release. Read more

10 recently open-sourced products from big tech companies

Releasing internal products to the open-source community is the hip new thing for technology giants to do Read more