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

Exactly what point would this be when the application that kicked all this off is about as non-native on any platform as you can get? There's a certain irony there.


We aren't talking about Chrome. Chrom ekickstarted the discussion on consistency - this article isn't about Chrome at all.

Reply Parent Score: 1

RE[4]: OMG
by dagw on Mon 16th Feb 2009 18:07 in reply to "RE[3]: OMG"
dagw Member since:
2005-07-06

We aren't talking about Chrome. Chrom ekickstarted the discussion on consistency - this article isn't about Chrome at all.

But his underlying point is valid to the discussion. Just because all your apps use the same underlying toolkit is in now way a guarantee for a consistent experience. Chrome is just the illustrating example.

Reply Parent Score: 4