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 348871
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why not QT?
by deb2006 on Sat 14th Feb 2009 14:03 UTC in reply to "Why not QT?"
deb2006
Member since:
2006-06-26


(...)
Besides Nokia who now owns TrollTech is making QT work under LGPL license...
(...)


That's gonna be one major obstacle for Qt in the future. Do you trust Nokia? Well, I don't. Not a bit. And therefore I'd advise anyone to use GTK+ when it comes to new open source software projects. It's basically the same situation before GTK+ appeared - now with Nokia only worse. Sorry.

Edited 2009-02-14 14:05 UTC

Reply Parent Score: -2

RE[2]: Why not QT?
by danieldk on Sat 14th Feb 2009 14:13 in reply to "RE: Why not QT?"
danieldk Member since:
2005-11-18

That's gonna be one major obstacle for Qt in the future. Do you trust Nokia? Well, I don't. Not a bit. And therefore I'd advise anyone to use GTK+ when it comes to new open source software projects. It's basically the same situation before GTK+ appeared - now with Nokia only worse. Sorry.


Right, and what harm could they possibly do? When Qt 4.5 is under the LGPL, anyone could take the LGPLed source and continue the efforts if Qt would somehow stagnate under Nokia.

In reality I see the opposite happening: Qt seems to have accelerated over the past year.

Reply Parent Score: 12

RE[2]: Why not QT?
by segedunum on Sat 14th Feb 2009 15:06 in reply to "RE: Why not QT?"
segedunum Member since:
2005-07-06

That's gonna be one major obstacle for Qt in the future. Do you trust Nokia? Well, I don't. Not a bit.

Hmmmmmm. But it was OK when Nokia were contributing, and still are, to GTK and you have the main GTK repository pretty much dominated by Red Hat with a bottleneck of bugs going back years that aren't personally interesting to them?

I really was curious as to what people would get off the bottom of the barrel, and now I know. "We don't trust Nokia, and, ermmm, it's not native!"

And therefore I'd advise anyone to use GTK+ when it comes to new open source software projects. It's basically the same situation before GTK+ appeared - now with Nokia only worse. Sorry.

Except that Nokia is making their repositories more open to external contributions now, and like GTK, if a situation gets untenable you fork it. It's also licensed under the LGPL now like GTK is, so you can get to do the exact same things with a fork and appease the 'develop for free' brigade.

Where do we go from here I wonder?

Reply Parent Score: 11