I think "touch xaml" is a very apt name!!! It will finally show the real target for it - touch devices. Though MS doesn't say it officially win8 was never designed with consideration for enterprises. It's main reason is to not allow iOS and Android capture the whole mobile market.
But when Ballmer will realize that the massive investments he put into win8 don't really pay off financially, he will return to enterprises (those that pay money for software) ... guess how, with a new version of xaml
So as I said earlier, I better keep writing Silverlight and port it directly to winNext, rather than SL => win8 => winNext.
I've read a bit of local deployment of win8 apps but as far as I'm concerned I wouldn't even bother to tell an IT guy about it ... win8 is clearly not designed for enterprises, local deployment is just a hack.
Would I still have to develop different versions of an winrt app for arm and x86 and phone, and then get charged 30% just so an user will find the app in AppStore?
If so, then I already know the answer, MS is working hard to achieve this interoperability when it will be achieved it will be irrelevant for most people who have already invested in writing code today! shouldn't a well thought ecosystem of frameworks have started with interoperability and then diversify? they started with distinct frameworks and then think about interoperability ...
The problems of LOBs in Win8 go beyond XAML and sharing screens - the deployment model, everything going through the store so MS will take 30% is not acceptable. Will I see some changes in the deployment choices?
I don't expect anything good for Silverlight, but that won't stop me writing new SL. I believe Ballmer is not that lost in the woods - is just cynical - he knows very well that enterprises are not moving to Win8, therefore Win8 is exclusively for home consumers. The MS marketing machine just doesn't say it explicitly for obvious reasons, but I don't believe Win8 was ever intended to bring touch to enterprises. I see all Win8 editions (and in general the touch support) as just a teaser for enterprises, so that the dark empire will learn what enterprises need from an OS with touch.
Given the very slow pace at which companies are moving between windows versions, their thinking is that enterprises can stay as they are, eventually migrating to Win7 en-mass, running existing non-win8 applications and no problem. Even with a very good OS directed at them they won't migrate - so better get win8 out quickly, see how it goes and from 2014 we start talking about win9Next- enterprises will then move straight to winNext sometime in 2015, skipping win8. They wouldn't lose anything ...
But what MS should realize is that LOBs that are now done in HTML/JS are less likely to bring windows business in the future. Only sadists in MS dreams are going the route of WinJS in Win8. Had these apps been done in Silverlight, the windows ecosystem in winNext would have benefited much more. What would have ensured an even bigger slice of Win8 in enterprise is SL changed to run in Win8 - I suspect a Win8 theme or a special sandbox for running SL in Win8 shouldn't be such a big problem for a company with tens of thousands of programmers!
Time will tell where these win8 apps today will be in 2-3 years ... when I'm pretty sure I'd need to port them again to the next OS model. So I better keep writing SL and port only SL to winNext, rather than SL => win8 => winNext.