The new direction of Microsoft Internet Explorer 10 (IE10) and the Windows 8/Metro platform suggests that external plug-ins will be given less of a role. Doing without plug-ins will be a shock for developers. It's a huge change but, I believe, a good thing.
Metro Rethinks the Browser
In Windows 8, there are two flavors of IE10 a desktop application and a Metro-style application. The desktop version of IE10 will be as it has always been: It will support plug-ins, tabs, and more. The Metro version, however, will not accept plug-ins. As you may know, the Metro UI in Windows 8 is an optional view of the operating system in which applications run in full-screen mode hiding the classic operating system chrome just as it runs in mobile operating systems. Metro applications mimic smartphone applications in their being user-centric, mobile-oriented, and endowed with specialized filesystems.
Among other things, doing without plug-ins should improve battery life and reduce security risks to zero.
The server-side application provides data feeds. The immensely popular jQuery library helps glue together other features that the browser makes available. So what about the BOM? At present, it incorporates Ajax and geolocation capabilities. Starting with HTML5, the BOM will include even more enticing capabilities, such as Web sockets, canvas, and local storage. Any new features the browser has to offer can be used by libraries such as jQuery to offer new programming facilities thus making developers' lives easier and pushing them to implement new ideas and tools. A richer BOM is much better than a browser with plug-ins.
HTML5 Pushes a Plug-in-free World
I have nothing against plug-ins and I did some Silverlight programming myself over the past few years. My company still keeps deriving business from Flash animations. However, we're looking (well, not just looking…) into Windows 8 and Metro for evolving our mobile front-ends, tools, and frameworks.
HTML5 and its set of companion standards (Web sockets, geolocation, local storage, offline apps) reinforces the browser and with it the pillars of the Web the HTML language and HTTP protocol. If we can render rich graphics and connect to any endpoint over ports, we don't need plug-ins any more. Such an HTML5-only approach is good for consumers, too, as it makes it simpler for producers to provide a comprehensive and ubiquitous (and why not touch-first?) browsing experience.
And Then, Silverlight…
Since the public announcement of Windows 8 and Metro in September 2011, removing plug-ins from the Metro version of IE10 has generated a lot of comments. In the Microsoft community, fear and uncertainty about the fate of Silverlight 5 reigned for months. "Should I go with HTML5 or stay around Silverlight?" that's been, and still it is, a hot question.
I don't believe Silverlight and Flash will disappear overnight they still work and are still useful in many applications and scenarios. As an architect or project lead, though, your primary responsibility is driving your company towards the best technology choices. In this regard, a Web client that is not dependent on plug-ins is preferable and represents an important step forward. The HTML5 solution makes you cross-platform and mobile-ready from day one.
Dino Esposito is a frequent contributor to Dr. Dobb's. His most recent book, Programming Microsoft ASP.NET MVC was published by Microsoft Press.