Language Selection

English French German Italian Portuguese Spanish

Best alternative Linux desktops: 5 reviewed and rated

Filed under
Software

The desktop on your Linux box used to stand for something very simple. If you were a KDE user, you valued control, power and the ability to customise.

In rough terms, if you used Gnome you wanted the desktop to get out of the way so you could get on with using your computer. If you used anything else, such as Xfce, LXDE or TekWM, you were running an ancient machine that would struggle with either of the big two of KDE and Gnome.

The change brought about by the release of KDE 4 changed all that. To compete, Gnome threw away its years of solidity for a new way of working; Unity arrived, with similar features to Gnome 3 but with the aim of tempting users away from Mac and Windows.

Brave as they were, these designs had much wrong with them, especially in the months following their release. Various products arrived to fill the gap.

rest here




More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.