Notice I didn't say WinPhone8, I just said 'future Windows Phone'. I lean towards agreeing with you that WinPhone8 is too soon to remove the Silverlight based dev platform. And when a new platform (non-Silverlight is supported), hopefully the Silverlight option will exists for those who want it, and most importantly, for backward compatibility. I worry about the backward compatibility stuff... for example, I read that Windows 8 on ARM may not run all Intel based Windows apps, which could include things like Office or VFP. Then much of the benefits of a Windows based tablet are removed, being able to only run tablet specific apps.

>You may be right, but I can't see Silverlight being totally thrown out in WP8. Too many apps would immediately stop working.
>
>As for generated Javascript, I'm not sure that's good or bad. Generated code often is crap. And it would still be a debugging nightmare.
>
>>Excluded is what I meant. I don't think Silverlight will be part of future Windows Phone development. I expect Windows Phone will eventually be based on the Windows code base and you will still use .NET to create apps. I think you can use a WPF layer based on .NET or an HTML5 web based layer that still uses .NET to create. I think what is confusing developers since the Win8 demo/announcement is that even though native Win8 UI touch apps are HTML5 based, you will likely be able to build an HTML5 based app without having to code any HTML5/JavaScript (it would be generated).