The fact that you put Ruby and Python in your list shows that you're not up to date on UI technology.
Furthermore, all of them can host modules written in "toy languages." Word and Excel are extended by VBS and C#. Autocad is extended by C# and AutoLisp.
WebKit, chrome, firefox are C++ and probably so are tons of other apps/libs.
The difficult part is that there is no current team to do so, but some of the current devs may be willing to continue work in a leadership position of the OSS effort after the next rounds of layoffs.
Alternatively, a company could be formed (YC12?) to continue coding QT, and offer support + training. Hell, I'm tempted ;)
My fear is that Nokia will let future development languish and/or restrict future commercial licenses. Nokia's track record to date hasn't shown anything this evil, but you never can tell.
We only just got done porting them all from Fortran!
Now that I think of it, I'm happy with a C + high-level language future, and C++ programmers should pick up one or both of them.
Neither C# nor Java offer tangible benefits over C++ for me. I don't learn anything new, I just have to memorize new APIs. Terribly wasteful.
The real question is how screwed are C++ developers in general?
MSFT's offering is switch to managed C++/C++ CLR and use WPF - two doomed technologies together. Or there is always MFC
Apple say don't even try with C++ just switch to objective C
Your only choice is GTK (from C) and plug into the rich commercial opportunities of Gnome and Linux on the desktop.
So is C++ on the desktop dead?