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 349602
To read all comments associated with this story, please click here.
Member since:

Based on the link you gave, I think you'll find that from the list of frameworks listed for OSX, only one is still active... The other 3 were frameworks for OS 9 and below...

Carbon wasn't listed however, but that is being phased out too, so on OS X currently there is only Cocoa from Snow Leopard onwards (some will argue you could still use Carbon, but it is limited in 64bit environments)...

You can use Gtk+ or Qt if you choose too, but they aren't "Native"... You can use Swing for Java too (or SWT), Flash, Silverlight and I'm sure there are others too...

Reply Parent Score: 2