Where does Windows 8 leave the HTML5/Silverlight battle? 

Tuesday, September 13, 2011 5:50 PM

So //build/ is underway and there have been some significant announcements (yeah, the Samsung slate is probably the favorite among the attendees). The biggest announcement in my opinion which is game changing is ‘WinRT’, the Windows Runtime. Yes, there are other significant announcements like the support of various form factors (to lay the argument of head-on competing with the iPad to rest) and the new OS is backward compatible to Windows 7 (how can that not be? we are not talking Apple), but those are not the differentiators.

The differentiator is the eco system and with WinRT the entire Microsoft platform eco system centers around this runtime. Microsoft has tried that in the past with various versions of .NET Framework, but what was achieved was always a subset or a superset for various form factors. For the first time it seems we have the same runtime for all form factors (I have not had my hand on Windows 8 Preview yet and so could be wrong). If that is true what do we have?

We have the ability to code applications using XAML + any language of choice from C#, VB, C++ or HTML5 + JavaScript for the UI. The plumbing is taken care by the .NET Framework. In the new reality of cloud computing and web services, the UI/UX is the main responsibility of the various client devices (PC, Tablets, Phones). Obviously the client needs to be as rich as possible with the plumbing aspects built into the runtime that facilitates easy plumbing to the cloud/web services and that is exactly what the WinRT achieves.

So where does that leave the HTML5/Silverlight battle? Well, Silverlight (XAML + C#/VB) is more Microsoft, whereas HTML5+JavaScript is more non-Microsoft. The Silverlight loyalist will continue on, what needs to be seen is, will the HTML5+JavaScript community with a strong inclination to JQuery and other JavaScript Frameworks/Libraries swing?

Share This Using Popular Bookmarking Services
Comments are closed on this post.