>I'd say MS has the NEED - otherwise the ARM side of Win8 is doomed IMHO.
>Making XNA/C# dev less than first class seat as developer, as is hinted for WP8 (C and C++ rules again)

I don't know where you got this idea. C# is still very much a first class citizen. What Microsoft did, was make it easier for C++ to use XAML, and other technologies. They didn't reduce the role of C# in any way.

>will drive a stake through future earnings - silverlight getting shafted instead of enforcing Xamarin was bad,

Huh? Xamarin? What does that have to do with Microsoft? If you're implying Moonlight, that's pretty much dead. Xamarin's agreement with Novell/Attachmate did not include Moonlight. Xamarin has no plans to do anything with Moonlight.

>if Dotnet/C# is kept from WP8 developers it will get better memory usage (a plus at first) but put back development.
>
>Perhaps MS should have earmarked more CPU cycles for better code quality of compiled/linked app
>instead of squandering it away on code generation, which is a bad way to go IMHO IAC.

I don't even know what you're saying here.

>Giving the nuts of current WP7,5 owners the technologically "needed" squeeze
>of a stay at WP7.x will even shoo away willing Nokia fan-seniors ;-)
>Even if MS woke up and realized taht mult-core ARM has been planned for since 2006
>and mSDHC is a plus there are many ways for them to botch mobile, even if WP has many good sides now.
>
>The diehard WP7 laudators here have been awfully quit as Nokia sales were not really spectacular.