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.
Thread beginning with comment 349268
To view parent comment, click here.
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"
Darkmage
Member since:
2006-10-20

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

RE[2]: We're Stuck With It
by segedunum on Mon 16th Feb 2009 15:46 in reply to "RE: We're Stuck With It"
segedunum Member since:
2005-07-06

...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.

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

RE[3]: We're Stuck With It
by Lousewort on Mon 16th Feb 2009 18:32 in reply to "RE[2]: We're Stuck With It"
Lousewort Member since:
2006-09-12

"...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.

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.
"

Call it sad if you will, but QT license does get in the way;
We develop a suite of apps for our local investor community. We don't charge for the software, but provide it as a means to accessing the exchange data which we do sell.
Our current target platform is Windows. Of course, the platform and libraries do come at a cost, but it's a cost the customer is very willing to pay. They take it for granted.
Were we to adopt QT, we would have to charge a fee for each instance of our application suite; where our customers pay nothing right now, the QT app would cost them more than the Microsoft one- guess which one they would choose?
Conversely, our adopting the GTK allows us to continue to provide the app at zero cost to our client base; the choice is up to them whether they run Microsoft or Linux, without any cost implication.
I strongly suspect a similar reasoning for Google-Chrome.

Edited 2009-02-16 18:37 UTC

Reply Parent Score: 2