There has been a lot of discussion lately about the current status of Microsoft UX strategy and where is it going. Microsoft reps keep on with the same story of "depends" and away from concrete answers, they keep adding their own weight of uncertainty into the whole equation.
My pal, Scott Barnes, has been probably the most vocal among the outsiders (even though he was an insider not long ago) and making use of his position in the community, he has been reviving the waters of an old discussion. Where is Microsoft.UX going next... what is happening with WPF and, for what is worth, where does Silverlight fits in the whole equation?
To no one is a secret that HTML5 + CSS3 + JS are poised to the be the future of the interaction technologies, not only is the true open cross platform equation, their feature set have been gaining more and more power lately, to the point that it is been brought at par with a lot of its plugin counterparts… it might not be there in full right now... but believe me, it is going to get there very quick.
But the story doesn't end here, there is more to the interaction experience than just web. We need tools and frameworks that let us reap the benefits of the hardware beneath and that of the great user experience that (some) platforms provide, and it's for those scenarios that we wonder: what'd be Microsoft's take?
Enter XAML + C++
Among some slides posted today by Mary-Jo Foley about the new Windows Embedded Compact relase, a few interesting bits where shown… imagine you can take the power of XAML-based UX with the power and reach of native execution. No more performance issues, fat-out frameworks in the middle and as the slides put it no Garbage Collector pauses like in Managed Code.

Now keep in mind these slides are referring to the new Windows Embedded Compact released yesterday and it's not an official announcement of bigger proportions, yet… but it might be what has been missing to bring Windows + Dev units together within Microsoft and help start fresh with a more cohesive story… parallel to HTML5… and for togheter, to build some trust and show us a clearer future.
I know this might not be the best scenario for everyone, but it might be right scenario to move native development further… .NET is one the most ubiquitous development platforms in the Windows world and with Mono doing the dirty work no one at Microsoft have wanted to address… their footprint is pretty much everywhere. But .NET has it's limitations and Microsoft has been aware of them ever since they reset Longhorns from what-is-was-supposed-to-be to what-Vista-ended-up-being. XAML was probably the best outcome from that effort and it has prove to be a great DSL for UX development.
Back to the future, Windows 8 is just around the corner, coming along with its ARM and x86 flavors, it's supposed to be all about tablet support, energy efficiency and for what's worth it will be the tiding bone between a true cloud driven experience across all 3 screens… if anything we will need portability and we will need increased performance… away from all the cluttered bits in the middle and that's what XAML + C++ could bring to the party.
What do you think? Os this too crazy? or is Microsoft lost… still?
One thing is for sure, whatever Microsoft is set to release next I wished it came with a clear proposition of unity, an homogenized strategy and best of all something we, developers and designers (don't forget about those), can really believe in, not for a season or two but for years to come.