Linked by Thom Holwerda on Sun 23rd Sep 2007 13:43 UTC
Ubuntu, Kubuntu, Xubuntu Just like Eugenia yesterday, I also upgraded my laptop's Ubuntu Feisty installation to Gutsy a few days ago. The upgrade process went completely awry, though, so I was forced to do a fresh install. Not a bad thing, as it gave me the opportunity to take a look at Ubuntu's soon-to-be-released Gutsy Gibbon with GNOME 2.20
Thread beginning with comment 273825
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

You are technically right, but there are historical reasons for that. As far as I remember: QT toolkit was the first serious UI toolkit available on Linux, but was not free software at the time. So people begun to code a fully free alternative - GTK. When GTK was ready (and QT became free), there was already a lot of QT code around, so the split stayed there.

Why didn't the GTK guys wrote a free QT clone (so that apps could be ported) instead of reinventing their own toolkit, I don't know.

Reply Parent Score: 2

sorpigal Member since:

GTK was not written from scratch to compete with QT. At the time QT was being used as the foundation of KDE and Stallman and other zealous folks decided that a closed source toolkit just Would Not Do GTK was already existent and was in fact the most mature toolkit available under a free license. GTK started its life long before KDE chose QT and that was as the toolkit for the GIMP (it's in the name: GTK == Gimp Tool Kit). The GIMP developers needed their own toolkit because the TKs available to them at the time did not support the rather advanced stuff they needed for their image editor.

Eventually a Clone-QT project was started and it is precisely because this project was nearing completion that Trolltech GPL'd QT for Linux. And when the GPL'd Linux version of QT was *almost* finished being ported to Windows they GPL'd the Windows version as well.

The major thing dividing the two camps is and has always been C vs. C++ and not so much a license thing. The licensing problem was a very real problem only for the first year or two. Some kind of accommodation or merger would probably have begun, except that C developers hate C++ and C++ developers hate C. This is the one major reason you will never, ever see GTK and QT join together.

Reply Parent Score: 2

netpython Member since:

Thereis GTK and GTK+

Reply Parent Score: 2