Full disclosure: I'm a Qt developer both as a hobby, and for my work

FWIW, this thread did make me think a bit, apparant closed-mindedness of some of the participants aside, it's been a fairly interesting discussion, and some interesting points have been raised I think.

When considering the openness of Qt, it's worth keeping in mind the KDE community has influence there in that it's probably one of the largest group of Qt developers in existance, and Qt itself is LGPL'd.

(This is also entirely discounting the fledgling but undoubtedly soon-to-grow MeeGo/other mobile OS community around Qt)

That is, if there was some kind of a sinister plot to take Qt in directions that the community wasn't happy with, I think the community would soon take things their own direction again. Obviously, this isn't something that the controlling company would be looking to start, so I don't see this as too high a risk.

It's also worth reflecting on the decisions Nokia has been making on behalf of Qt (and other projects, such as MeeGo) so far. You're considering them a sinister overlord, but as far as I can tell, their actions have been benevolent at best, and a bit misguided at worst when they have made genuinely bad decisions (like the DUI/Orbit/Qt confusion).

There are other technical aspects of some of the posts here that I don't think are quite on for similar reasons, like "moc being a tie-in to Qt" which is just stupid - obviously, if you use a platform, you're tied to it - try using a Gtk+ app without using Gtk+.

I could go on, but I think I've written enough for now.

At the end of the day, if you're not happy with the situation as it is, get involved. Help develop Qt, help shape the tools, help make things happen - don't sit in an armchair and paint the bikeshed.