I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Microsoft has recently been promoting Silverlight out-of-browser as the recommended way to write desktop apps, instead of WPF. I suppose in a few years they'll be telling us that desktop apps should be HTML5 out-of-browser. That will be like nailing your testicles to your lower lip.
As a former MFC programmer for over 12 years, Qt was a huge improvement for me. I find it similar to MFC in some ways so the learning curve was not too bad. The biggest advantage is it gives me the ability to write code and without many changes in the code or much effort in the build system (since I pair Qt with CMake) I can also target for linux and macintosh. I do government funded medical imaging research so a lot of what I do should be public domain if any of my peers ask for it.
Other huge advantages are signals and slots and the UI. Being able to generate dialogs and other UI elements in code, through an editor or from a xml file is very convenient. Layouts and dynamic resizing are much better than what I had with MFC in VS 2005 and lower.
The biggest negative I have found with Qt is that the 750+ thousand lines of MFC code I wrote before that has to be ported to be used with the free version of Qt. Although a considerable percentage of that code is stuff that was not in MFC so I had to roll my own (or modify codeproject examples) but this functionality comes standard in Qt. Maybe not as advanced but the standard code is good enough to use.
"Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
I included Win32 although I only really use it via P/Invoke.
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!