A lot of reactions started on Twitter this morning following the publication of the article titled “The Future of Silverlight” on the Silverlight Team Blog. One that caught my attention was written by Hadi Hariri:
After a few messages I realized that he was talking about Silverlight.
The problems Silverlight addresses
The official announcement says between the lines:
… Silverlight enables applications that deliver the kinds of rich experiences users want. We group these into three broad categories: premium media experiences, consumer apps and games, and business/enterprise apps.
Even in their own statement, they acknowledge that Silverlight is not for building web apps, but is to address very specific features that you don’t have in HTML/CSS/JS.
Most of the features of Silverlight are already included in HTML
Silverlight is more than the browser
The article finishes with that emphasis: “Silverlight is much more than a browser technology”. Sure it allows you to build “out of the browser” apps, even desktop apps, and now Windows Phone 7 apps. I think this is a great advantage for developers that build desktop apps, but I just don’t see Silverlight as a web application technology.
What is Silverlight really for?
If you asked me where I would use Silverlight I’d answer:
- To build desktop applications
- To build Windows Phone 7 native applications
- And to build islands of interactivity of web applications, where the current “simpler and more standard” technologies are not enough, like in media applications.
And I think this is also how Microsoft should market it: a technology that allows you to create rich “web-looking” applications on the desktop, complex video components for the web , and to reuse the same skills to build native mobile applications for Windows Phone 7. But they should stop comparing Silverlight to HTML5.
What are your opinions on this topic? Please share them on the comments.