It’s not just about quality. It’s also that I insist that my applications have a consistent look and feel.
Qt, GTK+ 2.x, and GTK+ 3.x are the only mainstream toolkits for a Linux desktop which people aim to unify theming across, so it has to be one of those.
GTK+ 2.x is a legacy solution on life support, so that’s not an option.
GTK+ 3.x has a whole host of problems:
- Unstable theming APIs driving away developers of themes I like and limiting QGnomePlatform to themes which have been manually ported from GTK+ to Qt (unlike QGtkStyle).
- Buggy, regression-prone support for hiding GNOME-isms outside GNOME 3 (If I open a GTK+ 3.x app on my desktop, it’ll show the traditional and unified “for putting a menu button in the titlebar” menu bars simultaneously)
- Gleefully embracing UX decisions which defy decades of HCI research (like putting action buttons in the titlebar “because wasted space” rather than letting natural reading flow place them in the “end of last line on page” corner)
By process of elimination, even if it were inferior, I’d sooner wrap Qt in a nicer API than use GTK+ 3.x.