Linked by Thom Holwerda on Sun 23rd Sep 2007 13:43 UTC
Permalink for comment 273870
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 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-11-02
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.