"This document was created to show non-KDE people what they're missing - and if you haven't used KDE a lot, you're missing a lot of things and you may interested in reading this page to learn how many wonderful things you've been missing. I promise, this is a subjective analysis of why KDE rules. I was a GNOME user for a long time, one of those users who loved GNOME UI, and I didn't know how much things I was missing with KDE until I tried it."
To read all comments associated with this story, please click here.
Member since:2005-07-08
dcop = dbus. Granted, dcop was there first, and has been there for a long time, but look at the present and (most importantly) the future.
Which is why I said that KDE is moving to dbus. By the way: The infrastructure is less important, what matters is how many apps are using such infraetructure. And KDE really rocks on that field - all KDE apps used dcop to some degree, but sadly not all gnome apps are using it extensively.
kparts = uh... really, why? Isn't it just an inflexible way of embedding controls?
Not at all: Take a look at the amarok + wikipedia screenshot. The "<-" "->" buttons are there but in a different size, they could have even been removed. I don't see why it's "inflexible" or why it has not sense..
"Isn't it a big advantage over using Qt link solutions that can only be used by the KDE project?
This is FUD. QT is licensed under the GPL license and you can build whatever you want as long as you don't break the GPL license. You've to pay extra fees if you want a commercial license, right. I'm *shocked* that people sees this as a problem. Aren't we supposed to build free software? What's the point of having created the GNU project if you only seem to care about comercial apps being developed....?
Edited 2005-12-30 14:56
Member since:
I guess someone should provide a "why gnome rocks" document. I really hope someone will... But really:
dcop = dbus. Granted, dcop was there first, and has been there for a long time, but look at the present and (most importantly) the future.
kioslaves = gnome-vfs (yes, I can open something over an ftp, ssh, samba, etc... connection in gedit and just press "ctrl-s")
kparts = uh... really, why? Isn't it just an inflexible way of embedding controls? If I wanted to use gtkhtml (which I don't, I'll give you that...), I can do that right now. Sure, there's no unified way for doing such a thing. Instead every 'part' that wants to be embedded provides it's own specialised, optimised way of doing it.
And to all those people crying "DBUS, Cairo and GStreamer aren't Gnome projects!!! No Fair!!!!"... Please, where's the 'Open Source' in that argument. Isn't it a good thing that the Gnome folks are collaborating, aggregating and integrating other great Open Source technologies? Isn't it a big advantage over using Qt link solutions that can only be used by the KDE project? It's scary seeing people using arguments like that AGAINST gnome...