How Microsoft built a new web rendering engine for Project Spartan and IE on Windows 10
Context & Ripple Effects
This MSDN post by Charles Morris is the engineering-side account of a story that has been building since December's leaked reports of a lightweight 'Spartan' browser for Windows 10. In January, a technical deep dive explained how Microsoft created the new EdgeHTML rendering engine behind Spartan, and coverage of Internet Explorer being kept alongside Spartan for enterprise sites established that Windows 10 would carry two browsers.
What changed by late March was the split itself: Microsoft confirmed Spartan would ship with the new Edge engine while IE 11 retains the legacy Trident engine. This article explains how that new engine was actually built — the piece that makes the dual-browser strategy technically credible rather than just a product announcement.
First-order effects
- Windows 10 users get two distinct browsers out of the box: Project Spartan on the new engine for everyday browsing, and IE 11 on Trident aimed at enterprise compatibility — site owners now have two Microsoft rendering paths to test against.
- Microsoft's own engineering teams are committed to maintaining both engines in parallel, since the March strategy explicitly assigns each browser a different one.
Second-order effects
- The enterprise-compatibility carve-out lowers the main blocker to Spartan adoption inside organizations, forcing the question of when IT departments can retire their Trident dependencies rather than whether they must.
- A genuinely new engine entering the market pressures other browser makers' compatibility testing matrices and gives web developers a fresh non-legacy target to validate against.
Third-order effects
- If the pattern holds, Microsoft's browser line converges on the new engine as the default everywhere, with the legacy engine demoted to an enterprise-compatibility mode — a structural exit from carrying decades-old rendering code in the mainstream browser.
- Shipping a rebuilt engine as the foundation of a flagship OS release signals that rendering-engine investment becomes a differentiator again after years of treating it as commodity plumbing.
The trend: Microsoft is rebuilding its browser stack around a purpose-built new engine while quarantining its legacy engine for enterprise use — the first step toward consolidating Windows browsing on a single modern platform.