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.
Permalink for comment 349276
To read all comments associated with this story, please click here.
RE[2]: We're Stuck With It
by segedunum on Mon 16th Feb 2009 15:46 UTC in reply to "RE: We're Stuck With It"
Member since:
2005-07-06'll probably find the big boohaha over gtk+ being the one toolkit was it was the only lgpl licensed toolkit for ages and companies were too stingy to pay up to trolltech for the right to use QT.

It's one of the reasons given, but I've seen no Windows or Mac development companies getting interested in GTK+ because of the license. It was a really rather sad argument to make. It certainly lowers the barriers to entry, as it will with Qt, but picking up development tools out of interest and sticking with it are two different things. Maybe the Qt and KDE people aren't quite so self-conscious, I don't know.

Going back to the article, I just don't see how you will attract applications, and henceforth users, to your desktop and platform by advocating the 'one toolkit' route. It just limits the functionality you have available on a platform that is absolutely crying out for applications and users.

...although the gnustep people have been claiming that gnome did look into gnustep as a possible api for gnome before they finally settled on gtk.

If that's true then they need their heads examined. With the right investment of people and time GNUStep could have been so much more.

Reply Parent Score: 1