Despite the fact that many developers would welcome more rendering-engine compatibility, anyone expecting Microsoft to switch out its “Trident” engine and replace it with WebKit in Internet Explorer (IE) — especially in IE 8 — is misguided.
Comments this week by CEO Steve Ballmer set off speculation about Microsoft’s WebKit plans. Responding to a question during an appearance for the Australian development community, Ballmer said Microsoft could “from time to time take a look at” WebKit, the open-source rendering engine at the heart of the Apple Safari and Google Chrome browsers.
I can see a number of reasons Microsoft won’t be adopting WebKit any time soon — and not simply because introducing an open-source engine into a closed-source browser would set off many Softies’ alarm bells.
Just to be clear: I am not defending Microsoft’s decision to stick with Trident; I’m explaining what I believe to be the company’s philosophy around that decision. Here’s why I don’t see Microsoft switching allegiances to WebKit — at least not in the near term:
1. IE 8 is almost done, folks. Beta 2, which Microsoft released in August, is expected to be the final public beta. The final IE 8 is due before the end of the year — which I’ve interpreted and heard from sources meant “end of calendar 2008,” but I hear Microsoft might be claiming to be “end of fiscal 2009,” which would mean in the first half of 2009. In either case, Microsoft is not going to rip out Trident and replace it with WebKit at this late date.
2. Microsoft is pushing test cases, not rendering engines, as its best way to help ease developers’ compatibility headaches. Microsoft is releasing a growing set of test cases specific to IE as its preferred strategy for helping developers make sure their pages and apps will work with Microsoft’s browser.
http://blogs.zdnet.com/microsoft/?p=1705
Comments this week by CEO Steve Ballmer set off speculation about Microsoft’s WebKit plans. Responding to a question during an appearance for the Australian development community, Ballmer said Microsoft could “from time to time take a look at” WebKit, the open-source rendering engine at the heart of the Apple Safari and Google Chrome browsers.
I can see a number of reasons Microsoft won’t be adopting WebKit any time soon — and not simply because introducing an open-source engine into a closed-source browser would set off many Softies’ alarm bells.
Just to be clear: I am not defending Microsoft’s decision to stick with Trident; I’m explaining what I believe to be the company’s philosophy around that decision. Here’s why I don’t see Microsoft switching allegiances to WebKit — at least not in the near term:
1. IE 8 is almost done, folks. Beta 2, which Microsoft released in August, is expected to be the final public beta. The final IE 8 is due before the end of the year — which I’ve interpreted and heard from sources meant “end of calendar 2008,” but I hear Microsoft might be claiming to be “end of fiscal 2009,” which would mean in the first half of 2009. In either case, Microsoft is not going to rip out Trident and replace it with WebKit at this late date.
2. Microsoft is pushing test cases, not rendering engines, as its best way to help ease developers’ compatibility headaches. Microsoft is releasing a growing set of test cases specific to IE as its preferred strategy for helping developers make sure their pages and apps will work with Microsoft’s browser.
http://blogs.zdnet.com/microsoft/?p=1705