Tag Archives: KDE

Why I Switched to KDE

I have always been a Gnome person. I’ve tried KDE every once in a while but I never really liked it. It seemed it was always either features that were missing that Gnome had or things didn’t work right where they worked fine in Gnome.  I could never get used to it and I would always find myself back in Gnome.

Recently though, the timing was just right. I used to be a big fan of Unity, but I was very put off by the version that is in Ubuntu 11.10.  I liked the version in 11.04 much better. Not to mention it was much stabler. The version in 11.10 was very unstable for me and I did not like some of the new functionality. I quickly became very unhappy with Unity.  I realized that I wasn’t as big of a fan of Unity as I thought. I didn’t want to use Unity anymore I got so frustrated with it. So I started looking at my options.


I decided I would try KDE yet again. Not only did KDE look absolutely beautiful, but all of the features that were missing for me had been implemented and all of the deal breaking bugs had been fixed after many years. So I tried to give KDE a genuine shot. It was a bit awkward getting used to the way KDE does things. But I fell in love with it after just a few days and haven’t looked back. KDE seems very refreshing and freeing compared to Gnome. I can customize every little bit to my likings. Now I look back and Gnome seems very restrictive to me.


tl;dr: Got tired of Unity and tried KDE again. Fell in love with it and never looked back.

Why the hate for Qt?

I’ve noticed there seems to be a lot of “ZOMG it’s Qt! Oh Noes!” going on and I just don’t get it.  I think the reason is some confusion and lack of understanding.  Now I’m not talking about the programming languages behind Qt and GTK, I’m talking about the typical end user’s experience.  People seem to assume that Qt == KDE, Qt requires a lot of KDE libs, and/or Qt looks ugly and doesn’t integrate well in a GTK environment.

First, a Qt application doesn’t always mean it’s KDE.  Yes KDE is based on Qt, but there’s a huge difference between a pure Qt app and a KDE app.  An application that is written in pure Qt has nothing to do with KDE whatsoever.    Some of these include SMplayer, KeePassX, VLC (0.9.2), VirtualBox, and many others.  KDE apps will depend on a lot of KDE specific stuff that will have a lot of dependencies.  This goes on to the second point.  A pure Qt app does not require a tone of KDE libs since it has nothing to do with KDE.  All it usually needs libqt.

Finally to put this integration mess to rest.  Qt integrating into a GTK environment used to be an issue.  This is no longer true.  This argument is deprecated.  Qgtkstyle (which will come bundled with Qt 4.5 😀 ) is a Qt theme engine that uses your GTK theme directly.  It does not try to emulate a GTK theme or anything like that.  It actually uses the GTK theme.  So now it can’t be argued that Qt doesn’t integrate with GTK anymore.  You pretty much can’t tell the difference.

SMplayer Preferences
SMplayer Preferences

You almost can’t even tell those are Qt applications.

So I just don’t understand all the Qt hating going on.