Linked by Thom Holwerda on Sat 14th Feb 2009 12:55 UTC
Permalink for comment 349076
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2008-05-26
Does it really matter which toolkit has been selected, as long as it's a popular one? GTK is a good choice, Qt would have also been a good choice. In any case, we're getting a native Linux version and I'm sure the Qt fans will be able to implement an optional Qt interface for Chrome that you can enable by doing "./configure --enable-qt --disable-gtk".
What really matters is: Will Chrome for Linux be fast, will it render pages and run Javascripts correctly, will it accept D'n'D to and from KDE and Gnome programs, will it integrate with the accessibility features of both desktops, will it be stable and reliable, and how quickly will distributions adopt it or at least have it in their repositories?
That's what matters. Not what interface toolkit it uses. Most people run a mixed desktop anyway (GTK or GTK-alike programs on KDE, or Qt/KDE programs on Gnome/XFCE).