"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 view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:Well dbus was taken straight away from kde and then reprogrammed, now the kde people basically put their automation interfaces on top of dbus, so much for history,
DBus wasn't "reprogrammed". It was programmed from the ground up in C, with a design inspired, among other things, in the DCOP system. "taken straight away from KDE" is overdoing it a lot. Here for more info:
http://dbus.freedesktop.org/doc/dbus-faq.html#other-ipc
http://dbus.freedesktop.org/doc/dbus-faq.html#yet-more-ipc
cairo is not GNOME its an X project and used by both gnome anmd kde in the future,
Cairo is used right now in Gnome. GTK is using cairo since 2.8.0.
gstreamer has its roots also in other technologies like xine and the windows media api,
Xine is a player. There is no way in hell gstreamer shares similarities to xine beyond the use of third party media libraries (like ffmpeg).
Although GStreamer intends to offer the same features as APIs like DirectShow, their design is totally original. And when it comes to free software, there is no library that comes close to the level of features it provides for multimedia.
http://gstreamer.freedesktop.org/features/
It is usually like that, KDE has an interesting tech, gnome wants it reprograms it has often a worse solution, the kde people adjust their interfaces to the gnome solution to keep the peace ;-)
As is the case with Arts and GStreamer, mozilla and khtml, glib+Gtk and Qt (nice "interface adjustment there"), HAL, evolution-data-server, cairo and arthur (that was released later).
Yeah. "Usually". Hah.
Face it KDE is basically NextStep radically moved forward and basically really the only system besides OSX which is totally component oriented.
The day KDE is as usable as NextStep was in 1989 wake me up.
What a load of fanboyism.
Member since:"gstreamer has its roots also in other technologies like xine and the windows media api, but I agree that is pretty much the only area where gnome was first. "
you obviously know what you're talking about.....not. what do you think the g in gstreamer stands for? its a gnome technology, and always has been. gnome has been the first in about 70%-80% of the time. the ONLY time when gnome has gone after kde is with gparts. the rest of the time, kde has borrowed ideas from gnome.
Member since:
Well dbus was taken straight away from kde and then reprogrammed, now the kde people basically put their automation interfaces on top of dbus, so much for history,
cairo is not GNOME its an X project and used by both gnome anmd kde in the future, gstreamer has its roots also in other technologies like xine and the windows media api, but I agree that is pretty much the only area where gnome was first.
It is usually like that, KDE has an interesting tech, gnome wants it reprograms it has often a worse solution, the kde people adjust their interfaces to the gnome solution to keep the peace ;-)
Gnome still lacks a decent compound document model essential for any office package. The OLE clone BONOBO was a dead end road, due to the same design mistakes and OLE had and due to the flakey CORBA foundation (the kde people ditched corba way before BONOBO due to its slowness and flakeyness)
Well there now is a project which unifies KPARTs and gnome to some extend, thank god! That should have been done 5 years ago.
Face it KDE is basically NextStep radically moved forward and basically really the only system besides OSX which is totally component oriented.