Language Selection

English French German Italian Portuguese Spanish

Seven Things You Can Do in KDE (But Not on Other Linux Desktops)

Filed under
KDE

Today, Linux desktops have diverged to the point where exchanging one for another can feel like switching to another operating system. KDE is no exception. Although it remains the single most popular desktop, a higher percentage of desktops use GNOME technology, and for many users of GNOME, Linux Mint, or Unity, KDE might hardly exist.

At most, users of GNOME technology might have a vague impression of KDE. If pressed, they might say that KDE is configurable to a fault and offers a daunting array of features, in contrast to GNOME's minimalist approach. Too often, they dismiss KDE as being concerned only with eye-candy, claiming that GNOME is all about efficiency.

However, the awareness rarely goes further. Faced with a problem to solve, users of GNOME, Mint, or Unity will rarely think of KDE as an alternative, despite the fact that most KDE apps run almost as well in these interfaces as in KDE.

This limited vision is unfortunate, because KDE includes many features that have no counterpart in any corner of the GNOME ecosystem. For example, you can:

rest here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more