It has been known for some time that Microsoft plans to introduce a new rendering engine with the version of its Web browser that ships with Windows 10. Today's revelation indicates that the company could very well offer both browsers simultaneously, one as an alternative to the other.
Why would it do this? Well, Microsoft actually did ship two browsers once before, with Windows 8, both of which showed up in Task Manager as "Internet Explorer." One was for rendering Web pages on the Desktop, and the other was for rendering them in the other environment, which was then called "Metro."
Microsoft developers at that time communicated their hope that Web apps could be crafted in such a way that they could be installed in the Start Screens of both Windows 8 and Windows Phone 8, presenting themselves to the user of both classes of device as ordinary apps. The Metro IE would render these apps, while the WinRT runtime would render native Windows 8 apps.
Whether this was the only way or not, it was the strategy Microsoft chose for enabling Web-driven functionality for Windows 8. While that enablement might have worked, given enough time, the two-browser strategy failed because users found the duality too confusing. Some thought the Metro IE was confusing enough in itself.
Would Spartan help or hinder competition?
A two-browser strategy this time around would be for a different purpose: appealing to the user base so rapidly built up by Google Chrome, while maintaining a compatibility path with veteran Windows users.
However, Web developers have raised the issue of whether adding another rendering engine to the field will complicate matters for those preferring their sites and apps to look the same in every context. For years, developers have resorted to using pre-processor directives, macros or other techniques to identify the rendering engine of the client-side browser before serving it code. This way they can deliver code best suited for each engine, rather than serving up one framework and hoping for the best.
Opponents of a new Microsoft rendering engine say it would give them one more context to have to test for, thus complicating their work. But supporters counter that the plurality of Web engines currently in the field helps to ensure that all browsers adhere to standards. They cite past history, when Internet Explorer 6 had such a commanding usage share, and sites tested to render in IE6 appeared in Netscape or Safari as though an earthquake had hit them. With no one browser commanding the field, supporters say, developers no longer have to pick one as the prototype and hope the others will follow along.
Sign up for Computerworld eNewsletters.