There is certainly a strong connection between GTK and GNOME, just like there is a strong connection between Qt and KDE, but I still think it's going too far to call Skype a KDE app, or to call GIMP a GNOME app.
And you're right, there are free libraries and frameworks out there that can do much of what KDE libraries can do, and they can be combined into a free desktop, as shown by GNOME. But I still find that it goes to far when people call OpenOffice or Firefox GNOME apps.
My issue is not with the libraries, but with the very political and opportunistic GNOME direction changes and the lack of cohesiveness. Quite frankly, KDE has always been ahead at most technical issues, and still is. Now that there is no sane reason left to kill KDE (which was why GNOME was started), I am interested to see how it continues to develop. Is such a loosely-knit community where many important parts of the puzzle don't consider themselves a part of the GNOME project strong enough to catch up? It will be interesting to see.
Because all KDE apps can use GStreamer trivially (even the ones not based on Phonon, like Kaffeine and Amarok), just like they can use Cairo trivially. Or switch between webkit and KHTML trivially. Or use gdesklets or whatnot. So these technologies might be used by all GNOME apps, but they can just as easily be used by KDE apps. So I wonder again what GNOME brings to the table.
And you're right, there are free libraries and frameworks out there that can do much of what KDE libraries can do, and they can be combined into a free desktop, as shown by GNOME. But I still find that it goes to far when people call OpenOffice or Firefox GNOME apps.
My issue is not with the libraries, but with the very political and opportunistic GNOME direction changes and the lack of cohesiveness. Quite frankly, KDE has always been ahead at most technical issues, and still is. Now that there is no sane reason left to kill KDE (which was why GNOME was started), I am interested to see how it continues to develop. Is such a loosely-knit community where many important parts of the puzzle don't consider themselves a part of the GNOME project strong enough to catch up? It will be interesting to see.
Because all KDE apps can use GStreamer trivially (even the ones not based on Phonon, like Kaffeine and Amarok), just like they can use Cairo trivially. Or switch between webkit and KHTML trivially. Or use gdesklets or whatnot. So these technologies might be used by all GNOME apps, but they can just as easily be used by KDE apps. So I wonder again what GNOME brings to the table.
Comment