Linked by Thom Holwerda on Mon 16th Feb 2009 14:07 UTC
Editorial Late last week we ran a story on how the Google Chrome team had decided to use Gtk+ as the graphical toolkit for the Linux version of the Chrome web browser. It was a story that caused some serious debate on a variety of aspects, but in this short editorial, I want to focus on one aspect that came forward: the longing for consistency. Several people in the thread stated they were happy with Google's choice for purely selfish reasons: they use only Gtk+ applications on their GNOME desktops. Several people chimed in to say that Qt integrates nicely in a Gtk+ environment. While that may be true from a graphical point of view, that really isn't my problem with mixing toolkits. The issue goes a lot deeper than that.
E-mail Print r 2   · Read More · 93 Comment(s)
Thread beginning with comment 349323
To view parent comment, click here.
To read all comments associated with this story, please click here.
by michi on Mon 16th Feb 2009 19:43 UTC in reply to "KDE vs GNOME vs CHROME"
Member since:

KDE and GNOME experience are completely different - it is 'DECLARED APARTHEID'. Something that has gone unclaimed in South Africa, but in the Caribbean for instance, it's more alive than anything.

What? I think KDE and Gnome are actually quite similar. I use Windows, MacOS X and Linux regularly and in my opinion Windows, KDE and Gnome are quite similar. MacOS X needed some time getting used to it because of the menu bar on top and the concept that apps stay open even when the last window has been closed and Cmd- instead of Control-Key. I don't get why people think KDE and Gnome are so different. Both are designed quite similar and if you don't like the extra options KDE offers, just ignore them. Nobody forces you to use systemsettings to tweak everything. I ran KDE with all the default settings and I think it is quite o.k. No point in wasting time and modify stuff for the sake of it.

Reply Parent Score: 1