Language Selection

English French German Italian Portuguese Spanish

comparing "KDE 4" and "GNOME 3"

Filed under
KDE
Software

There is small trend currently to write a blog entry or article comparing "KDE 4" and "GNOME 3". Now, I'm not involved in the least with the GNOME 3 efforts (no big surprise there, I'm sure) so I can't and won't comment on what they are doing now or in the future (they can do so themselves quite well), but there are two interesting points I keep seeing raised that I really do want to address ... and I don't feel like commenting on every blog post out there. Wink

KDE 4 .. or the KDE Workspace?

What these blog entries are usually comparing is not "KDE 4" with "GNOME 3" but two of the KDE 4 workspace components, Plasma and KWin, with gnome-shell. Little more than that is compared in most of them when the topic is "KDE 4 or GNOME 3?". This is unfortunate because KDE 4 is a lot more than just the KDE Workspace, which is just one product that comes from KDE, just as GNOME 3 will be more than just gnome-shell.

A primary example is the KDE development platform. It consists of KDE's libraries built on top of Qt, Akonadi, Nepomuk/Strigi and others and represents one of the most important products we create. This platform started back in the 90s as a means to an end: getting the KDE desktop workspace functioning and sharing code and functionality efficiently between KDE apps in a way that guaranteed some consistency. These days, while it has kept this same set of purposes as an important part of its mission, the KDE development platform has taken on a much bigger role and a life of its own.

I'd love to see some thoughts that extend beyond Plasma/KWin out there and look at things such as the maturity of KDE's development platform compared to what others are offering right now or, as in the case of GNOME 3, in the near future.

Rest Here




Gnome 3

I sure hope Gnome developer don't mess up Gnome like the KDE developers did with KDE.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Linux on Servers

Debian, Devuan, and Ubuntu

  • My Free Software Activities in April 2016
    I handled a new LTS sponsor that wanted to see wheezy keep supporting armel and armhf. This was not part of our initial plans (set during last Debconf) and I thus mailed all teams that were impacted if we were to collectively decide that it was OK to support those architectures. While I was hoping to get a clear answer rather quickly, it turns out that we never managed to get an answer to the question from all parties. Instead the discussion drifted on the more general topic of how we handle sponsorship/funding in the LTS project.
  • Initial Planning For Ubuntu 16.10 Today At UOS
    Beyond the announcement that Ubuntu 16.10 won't ship with Mir and Unity 8 by default, many other items were discussed for the Ubuntu 16.10 release due out in October.
  • Ubuntu 16.10 Isn't Going To Use Mir / Unity 8 By Default
    Well, another setback for Unity 8 and Mir. Kicking off the Ubuntu Online Summit for Ubuntu 16.10, it's been confirmed that the Unity 8 desktop and Mir display server will not be the default for the desktop spin. Similar to the current situation with existing Ubuntu releases, Unity 8 and Mir will be available as an opt-in feature for users wanting to upgrade their desktop, but Unity 7 and the faithful X.Org Server is planned to be the default for Ubuntu 16.10 Yakkety Yak.
  • Devuan Beta Release
    After two years in development, a beta release of the Devuan distro has made it into the world (Devuan is a registered trademark of the Dyne.org foundation). Devuan is a very Debian-ish distro. In fact, it basically is Debian, with one notable absence. Devuan doesn't use systemd. In fact, that's its main claim to fame. Devuan was created to offer an alternative to Debian fans who were alienated by the controversial switch to systemd.

Leftovers: OSS

today's howtos