The situation is a wee bit different - those are missing from MeeGo (well, Unity3D was ported for MeeGo Harmattan, remember that Samurai game?) and Maemo not due to the inability for those platforms to support such, but due to way too small user base for Adobe/Unity/others to bother with. On WP 7.5/7.8/whatever-they-want-to-call-it no matter of the user base those cannot be supported on a system level - least Adobe wants to build a LLVM compiler that will spew .NET bytecode (and even then, it's questionable if the full feature set can be supported / used without specific run through VS to 'enrich' it with MS certificates and what-have-you) or Unity to implement it fully in XNA (which they cannot, that's why you can't really use Unity for Xbox games as well, unless you are AAA developer where Microsoft allows you native, direct access).

Both Adobe and Unity, and countless of others (including my own company) that provide some toolkits/libraries for cross-platform development will now be able to painlessly bring their solutions to the WP8 without running through loops n' bounds and restricting feature sets to fit in the tight requirements of WP7.x. That means that developers who utilize those 3rd party libraries/toolkits/whatever won't be able to target the WP7.x users so, while the WP8.x users will be getting those new apps and features, WP7.x users won't.

And that's the main problem that, I think, Cue was explaining. That's called fragmentation, a word used way too many times by MS shills to describe the perils of Android - isn't it ironic when it turns out and bites them in the arse? Since WP already has quite a number of .NET-based, WP7.x compatible apps, the next surge of apps for the WP platform will be coming from game developers that are eager to port their games easily and effortlessly (before, even if your game was XNA-based, the XNA for WP differed too much to be practical for back-porting to WP any moderately complex game) and application publishers who either utilize toolkits like Adobe AIR, Unity3D and the like; or write their apps in C/C++ so they can easily target all other platforms. Both of those won't be available for the WP7.x users so they'll be missing quite a lot - they are also too small of a user base, as well as Maemo/MeeGo, for companies to cater to their needs by writing apps from scratch just for them - they'll just ignore that market and that's it.

Think of it like this - BBC, when they launch their iPlayer for the WP, will most probably just use their shared code base to create close-to-native app for the WP8.x, and they'll apologize to the users of WP7.x by saying that it's way too complex/expensive to cover their needs as well. So, WP7.x users just got royally screwed, and the funniest bit is that Microsoft (and the apologists) are explaining that WP7.x won't be supporting native code because it's related to hardware (yes, they said that a ton of times!, as if app layer has to do anything with the hardware). Oh, well, as long as people are drinking the Microsoft Kool-Aid... Come fall, a different song will be sang by those way too enamored with WP and their precioussssses to see the harsh reality...