5 they are a property of the canvas).
Of course Silverlight is XAML-based and so is one of the programming models for Windows 8 metro. I am currently porting a Windows 7 Phone Silverlight app to Windows 8 as a pure Silverlight app. Much of the XAML moves to the new platform without change.
Because of this, I believe we should be discussing XAML solutions vs. HTML 5. I see a need for Silverlight to build robust business apps like in the medical industry. And, if properly designed, they can run in Windows 8 Metro. However, I must add that the Metro design is not good for developing apps like this and the Silverlight UX will need to be 'watered down' so the business app is better off in the old windows Desktop mode. I must say that I do not see the need to write desktop apps in this day and age.
The other issue is Silverlight vs. WPF. And here I really believe that WPF will gradually fade away, especially now that SL use XNA for its 3D graphics.
'One important thing to understand is Silverlight has a purposely limited role. For instance, while you can build Win 8 Desktop apps, it is useless for Metro.'
Not entirely accurate. I would say that Silverlight is simply one host for XAML applications, particularly pre-Windows 8. With Windows 8's Metro interface, your Silverlight apps (with relatively few changes) become native XAML Metro applications. Your 'Silverlight' applications continue to live on, now as native Metro applications, and will continue to live in the Silverlight host (at least through 2021) for non-Metro environments. That's a pretty optimistic picture if you ask me.