GNOME, GObject, Glib or KDE and Qt

[btiffin]

I'll admit to being confused.

Where is the mainstream drift? Back to good old C ABI and the G-side, or C++ and K-Q?

Hopefully not a belief based flamewar topic, as I don't really care either way and see the benefits in both (especially now that I've gotten over my fear of interfacing OpenCOBOL with the C++ ABI). Last year I had a sense that GNOME was following Betamax, but now, not so much. Am I hanging out in corners of the net that seem to lean toward the C ABI, or is KDE, Qt and C++ the overwhelming tools of choice for the future and I'm not seeing those sites? OR, are we destined to have the luxury of choosing either with expectations of both being around for the next 10 or so.

I can't get a tell on either one pulling ahead. Which would be a good thing, two strong, mainline dev environments with neither killing off the other. Not worrying if choices made are good longterm choices is better than nagging self doubt or blind running off of cliffs.

Thought I'd ask what the up and comers are picking. Thanks, if you have an opinion.

Cheers
Seriously, I'd like to see a "both" trend (don't care wouldn't be as nice...99% don't cares can be highly unpredictable) or a 50/50 split if staunch support of one and one only is the way things are rolling

[rdrake]

I'm biased towards GNOME. KDE really screwed up by releasing 4.0 when it was beta software at best. I also think KDE is an unusable, ugly mess.

That being said, Qt gives you the benefit of being available on pretty much every major platform. Not having any development experience with GTK+ or Qt I can't really provide any advice in that regard.