Linked by Thom Holwerda on Thu 2nd Apr 2009 16:12 UTC, submitted by Rahul
Gnome Only a few days ago, we ran an article on the future of KDE and GNOME, and which of the two had the brighter future based on their developmental processes. Barely has that discussion ended, or the GNOME engineering team comes with a pretty daunting plan to introduce a fairly massive reworking of the GNOME interface for GNOME 3.0 (2.30). Read on for the details.
E-mail Print r 15   · Read More · 127 Comment(s)
Thread beginning with comment 356437
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: you know what sucks?
by darknexus on Thu 2nd Apr 2009 17:17 UTC in reply to "you know what sucks?"
darknexus
Member since:
2008-07-15

Yes, I know what sucks. Everyone saying "GNOME should just use KDE this, ditch that in favor of KDE framework." Well, if they did that, we wouldn't have much variety now would we? No chance for innovation, for new ideas. Guys, KDE is not the end all be all.

Reply Parent Score: 10

RE[2]: you know what sucks?
by phoenix on Fri 3rd Apr 2009 06:34 in reply to "RE: you know what sucks?"
phoenix Member since:
2005-07-11

Yes, I know what sucks. Everyone saying "GNOME should just use KDE this, ditch that in favor of KDE framework." Well, if they did that, we wouldn't have much variety now would we? No chance for innovation, for new ideas. Guys, KDE is not the end all be all.


Interesting how the KDE/QT guys don't have (m)any problems with using GNOME/GTK technologies in the name of interoperabilty (dbus in place of dcop, using the glib event loop in qt, and there was another big one I can't recall atm), yet when someone suggests that GNOME/GTK use a KDE/QT technology it's like they're asking GNOME devs to sacrifice virgins to the volcano gods.

Reply Parent Score: 6

RE[3]: you know what sucks?
by abraxas on Sat 4th Apr 2009 16:31 in reply to "RE[2]: you know what sucks?"
abraxas Member since:
2005-07-07

Interesting how the KDE/QT guys don't have (m)any problems with using GNOME/GTK technologies in the name of interoperabilty (dbus in place of dcop, using the glib event loop in qt, and there was another big one I can't recall atm), yet when someone suggests that GNOME/GTK use a KDE/QT technology it's like they're asking GNOME devs to sacrifice virgins to the volcano gods.


It's a technological issue, not a religious/political issue. Integrating C++ components into a C environment is MUCH more difficult than doing it the other way around.

Reply Parent Score: 2

RE[2]: you know what sucks?
by superstoned on Fri 3rd Apr 2009 10:48 in reply to "RE: you know what sucks?"
superstoned Member since:
2005-07-07

I'm not saying the gnome devs should stop working on Gnome technology. I'm just saying they should think about using the right tool for the right job.

Sharing lower-level technology saves time for actual innovation. Duplication isn't good for innovation - if you need something and it's available, use it, so you can spend time on the implementation of the original part of your idea.

If gnome would start to build upon Qt and (some) KDE libraries, they would have more time to spend on innovation, finding new ways of doing things. They still have their own HIG and their own ideas about interfaces and usability - it wouldn't mean Gnome would become KDE or the other way around. It would just result in an accelleration of development for both and more innovation on the Free Desktop.

Something I would love to see.

Reply Parent Score: 1