Linked by Thom Holwerda on Sat 14th Feb 2009 12:55 UTC
Google A major complaint about Google's Chrome web browser has been that so far, it is still not available on anything other than Windows. Google promised to deliver Chrome to Mac OS X and Linux as well, but as it turns out, this is a little harder than they anticipated, Ben Goodger, Google's Chrome interface lead, has explained in an email. It has also been revealed what toolkit the Linux version of Chrome will use: Gtk+.
Thread beginning with comment 348898
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Why not QT?
by bnolsen on Sat 14th Feb 2009 15:23 UTC in reply to "RE[2]: Why not QT?"
bnolsen
Member since:
2006-01-06

<quote>(Qt 4.5 is fast on every platform.)</quote>

Wrong!

Qt fails when it comes to network transparency. This is true with remote X11 (unix) and terminal server (windows), especially when heavy rendering is required (cad/gis). Yes, an answer is to use vnc/remote desktop instead but they're not suitable replacements.

We dumped qt4 because of the above and if you go looking at the qt blogs a constant theme in the user comments is: "is this feature X going to speed up remote display"?

I was kind of hoping that google might take a shot at writing a better cross platform gui toolkit.

As it stands I certainly hope to see Qt truly shredded over the next 2 years as the old unecessary redundant portions written specifically for vendor lock in are replaced with better open/standard technologies. I'd say gtk is likely to be more stable in the upcoming couple of years.

Reply Parent Score: 5

RE[4]: Why not QT?
by ardor on Sun 15th Feb 2009 11:54 in reply to "RE[3]: Why not QT?"
ardor Member since:
2009-02-15

Technically, Qt is far superior to Gtk. QGraphicsView alone is one thing that you cannot do in Gtk without a significant amount of extra effort. The API, the tools (designer, linguist, creator..) and documentation are lightyears ahead of Gtk.

Also, what "unnecessary vendor lock ins" are there? You do realize that starting with 4.5, Qt will be LGPLed, right?

I have been writing scientific visualization software using Qt as the toolkit and OpenGL for real-time previews and editing. I would NEVER use the X protocol for network transparency. Instead, I wrote the application itself in a distributed way. There is no way you can use DRI OpenGL and X network transparency at the same time without ugly hacks. (And you *want* DRI with OpenGL.) Relying on the X protocol for heavy rendering is just *wrong*.

Reply Parent Score: 3