The Future of GTK+

by
in code on (#3Q6)
story imageOnce hailed as the most free and widest used X toolkit, the future of GTK+ now looks dire. The gnome developers have essentially highjacked the latest version, GTK3, and are actively destroying all ability of non-gnome users from using this once popular toolkit. I find this very unsettling, as I have developed a number of my own desktop applications using GTK+ through all three of its major versions. I've always preferred GTK over QT, but with some of the recent changes, I'm starting to change my mind.

Of course, I'm hardly alone in this opinion as many other projects have abandoned GTK in the recent months. Take Audacious, for example. This GTK music player has had increasing troubles with the gnome developers screwing things up. So many troubles that they are now planning on switching toolkits rather than further deal with the upstream management. Although they had a functional GTK3 port, they've officially reverted back to GTK2 until they can properly refactor their entire program into QT.

I've been a happy user of the XFCE desktop environment for the last few years. This light and easy to use UI gets out of the way and just plain works. However, the interface toolkit of XFCE is tied to GTK2 and its authors have no clear upgrade path. A similar project, LXDE, has also seen the writing on the wall and are well into a rewrite project that switches their preferred toolkit from GTK to QT.

Although the "G" in GTK stands for "GIMP" this popular image manipulation program has yet to release a GTK3 version. Even Linus Torvalds' own pet project, Subsurface, has recently abandoned GTK for QT. Is the future of GTK+ programs doomed? Can a revival project, such as Mate, takeover maintenance of the GTK toolkit for the rest of us? (let the gnome people screw up their own fork)

Re: KDE / Qt Always Better (Score: 1)

by mth@pipedot.org on 2014-07-10 01:18 (#2E1)

To me it looked like GNOME2 had better polish in both themes and apps, while KDE3 had better underlying tech (Qt, KIO, DCOP, KParts etc). It would probably be less of an effort for GTK theme writers to build a good looking Qt theme than to keep a themable GTK library alive, since the GNOME3 developers seem hostile to the very idea of theming the desktop.

I don't think the GNOME3 developers are necessarily wrong: you can't have a highly customizable desktop that also provides a consistent and instantly recognizable look and feel. KDE chose customization and accepted that not every combination of settings works equally well and that every distro's and person's KDE desktop looks and feels slightly different. GNOME3 seems to choose the other option, but doesn't go all the way and keeps a bit of customization limping along. In my opinion it would be better for everyone involved if they would just cut out the theming functionality altogether: the GNOME devs get to build their single consistent user experience while the theme authors would be spared the frustration of their themes being broken in every new GTK release.
Post Comment
Subject
Comment
Captcha
The list egg, tooth, library, hair, finger and ear contains how many body parts?