Problems run very deep on this issue
2) HTML5 is in flux, both in its specification and in its multi-vendor implementations. It will remain a moving technology target for at least the next year or so. This platform instability is of course problematic to those who know and value the realities of stable, serious application platforms.
3) By contrast, Silverlight and .NET are well proven, mature, very robustly developed, and revolve around world-class development languages, such as C#. To put it briefly, stacking up HTML5/JS against Silverlight/.NET is irresponsible, unrealistic, untenable, and frankly a joke.
4) Waiting until September to travel across the country and be evangelized by the BUILD conference not only is expensive, but it is completely unnecessary in order to disclose the pertinent details required now from Microsoft to maintain the developer community's trust and loyalty. Furthermore, the timing could not be worse (at least for everyone except Apple and Google), for various reasons that go well beyond the scope of this brief note.
5) The MSFT position on this "new" development platform (which is really not new at all in our experience), draws clear and serious lines of technical demarcation between WP7, Windows 8, and the Windows desktop, making application portability difficult at best between the three platforms if we are to remain committed to a seamless user experience and to robust systems that are affordable to develop and port.
The seasoned developer community which, at least for the vast majority of us, strongly objects to Microsoft's positioning and lack of information on this does problem, does not need to hear anything at this point from Microsoft except a relaxing of their exclusive dogma and instead replacing it with a continued commitment to Silverlight and .NET. We aren't interested in propaganda. We are interested in responsible, honest communication and real support.