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 349268
To read all comments associated with this story, please click here.
RE: We're Stuck With It
by Darkmage on Mon 16th Feb 2009 15:28 UTC in reply to "We're Stuck With It"
Member since:

you'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. That probably has had more to do with gtk adoption than any other factor. KDE was first on the scene as far as I am aware, 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. btw to be fully disclosed, I am currently writing a 3d modelling app in gtk+ 2.0 ported from gtk+1.2. (it's not easy to write apps in any language I've tried so far. (except vb but I didn't like how vb worked anyway.))

Edited 2009-02-16 15:30 UTC

Reply Parent Score: 1