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 349269
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: OMG
by steviant on Mon 16th Feb 2009 15:29 UTC in reply to "RE: OMG"
steviant
Member since:
2006-01-11

Oh come on, he does have a point... based on their bizarre interface in Windows, Google Chrome probably isn't going to feel right in KDE *or* Gnome, so it's hardly worth anyone getting up in arms about their choice of toolkit.

Apart from the fact that the poor sod completely missed the fact that you were talking about the issue of consistency, and not complaining about Chrome, it was a very relevant post. ;)

Reply Parent Score: 3

RE[3]: OMG
by xnoreq on Mon 16th Feb 2009 15:52 in reply to "RE[2]: OMG"
xnoreq Member since:
2009-01-06

Oh come on, he does have a point... based on their bizarre interface in Windows, Google Chrome probably isn't going to feel right in KDE *or* Gnome, so it's hardly worth anyone getting up in arms about their choice of toolkit.


That's exactly what I meant. It will probably be more inconsistent with other Gtk apps than Qt <-> Gtk apps!
So even if you use the super ability to stick to one toolkit only it won't give you a consistent desktop.

Reply Parent Score: 3