Well, it was 8 weeks later than we were told it was going to be but with the final release of Microsoft’s Silverlight on September 5th it’s only right that we talk about it. I’m a huge believer it what it has to offer, in fact so much so, that in a previous life I advocated delivering a Silverlight solution for Discovery Channel Asia back when it was still in beta – albeit a pre-release beta. The site was rolled out in July 07 was the first commercial application of Silverlight globally.
So what does Silverlight do? Why all the hype? Why would developers choose to develop on Silverlight that has limited penetration compared to the ubiquitous Flash that has close to 100% penetration. Well here are few reasons:
1) It’s a cross browser, cross platform presentation technology working seamlessly across Windows and Macintosh platforms.
2) It supports playback of WMV files on both PC and Macintosh and will deliver an optimised encoded video stream, depending on the available bandwidth, up to 720 dpi.
3) Silverlight supports seamless transitions between full-screen and windowed mode.
4) Silverlight includes a mini-CLR (Common Language Runtime) from .NET which means as with the usual .NET runtime, you can code in a number of supported programming languages – which means there are no special languages to learn – any developer can pick up Silverlight and start using it straightaway. For example, the Discovery Silverlight site took 2 weeks from first looking at Silverlight to delivering a working site.
5) Silverlight is a lightweight subset of XAML, the markup language, and by separating markup (XAML) from code, Microsoft has empowered designers and given them development control of the front end. This is important. An analogy that I’ve heard used by Microsoft is that of an egg. A design might start as a nicely formed egg that a client sees and buys into. That design is then handed off to a developer to code. Developers will have their own interpretation of the design and maybe there’s some elements of the design that just technically can’t work. The finished product, a broken egg, stuck together with sticky tape. Not what the client signed up for. What Silverlight does is empower the designers through their Expression Software suits. Designs instead of being saved in a JPEG or PSD format are created in XAML that are then handed of to the developers to integrate into the web page. The end result, a nicely designed Silverlight element, that looks exactly what the client signed off on.
6) Another key feature of Microsoft Silverlight is that it integrates seamlessly with HTML. Every XAML element can be accessed or manipulated from the same client-side JavaScript that would be used to interact with any DHTML element: there are no artificial boundaries or barriers. Unlike Flash that is self-contained element within a page.
7) The Silverlight plugin is also very small – only 1MB - and is also blindingly fast, being able to for example (depending on the bandwidth of course) play many videos simultaneously without stuttering or dropping frames.
8) Silverlight is both client- and server-agnostic – an element does not need to be specially encoded depending on the environment that it is going to run in nor does it need any specific software on the server.
9) Lastly, are Microsoft’s plans for Silverlight on the mobile. To date we’ve seen a demo that was created for the
MLB (Major League Baseball) that shows both Silverlight applications and media streaming running on a mobile phone - so Silverlight even at this stage is about more than just the desktop browser and desktop market.
Well that’s about it. If you want to see more it's worth checking out the
Silverlight site and if you want to see the site that was developed for Discovery then you can find it
here.