Mary Jo Foley at ZDNet reports that Microsoft is planning to release a new web browser with Windows 10. We have talked about it in the past, and its rumored extension architecture in particular, but it was expected to become Internet Explorer 12. Even then, snippets have shown that the team was considering a name change away from IE, to some degree of seriousness. Now we are hearing that it might actually be a wholly new, standalone browser that is installed alongside IE11.
Yikes. Okay, so…
Stick a fork in… … Trident…?
(Image Credit: Wikipedia)
Browser rendering engines have been in flux over the last couple of years. First, Opera decided to deprecate their Presto engine and move to Webkit, along with KDE, Apple, Google, Valve, and so forth. Later, Google decided to fork Webkit into Blink, with Opera following them, to push updates with less inter-company politics. Meanwhile, Mozilla (and Samsung) started a research project, called Servo, which was developed from scratch to be a multi-threaded, efficient rendering engine. This is difficult, because Web standards were designed to be single-threaded; it may be a successful replacement, or it may just teach them a few new tricks for Gecko.
Developing a new engine from scratch is daunting but Microsoft could obviously afford it, if it is deemed a worthy project. With Trident being forked, it seems unlikely for a while though. After all, why would they fork an engine if they had something in skunkworks for years (because a standards-compliant rendering engine takes a long time to make)? Chances are that they have no plans to even start, but don't let that belittle Microsoft's possibilities with a Trident fork that is free of legacy Internet Explorer concerns.
A preview of the new browser might not make the January technical preview of Windows 10, but it is expected to be done in time for Windows 10. We will probably have access to a pre-release version before then and they might even show it off during their Windows 10 Consumer event on January 21st.