In addition to Project Spartan, Windows 10 will include Internet Explorer for enterprise sites
Emil Protalinski / VentureBeat :
Context & Ripple Effects
The lightweight browser codenamed Spartan surfaced in December as Microsoft's clean break from Internet Explorer's codebase — no legacy baggage, and by late January it was confirmed to support extensions. Today's report adds the missing piece of the strategy: Windows 10 won't actually remove IE, keeping it available specifically for enterprise sites that still depend on old web technology.
That pairing resolves the tension between rebuilding the browser from scratch and not breaking corporate customers' line-of-business apps — the constraint that has historically kept Microsoft tied to its aging rendering stack.
First-order effects
- Enterprise IT gets a supported migration path: Windows 10 machines can run Project Spartan for the modern web while falling back to Internet Explorer for internal sites built against older standards.
- Microsoft commits to maintaining two browsers in one OS release, with IE explicitly repositioned as an enterprise-compatibility tool rather than the default consumer experience.
Second-order effects
- By March, Microsoft formalized the split at the engine level — Spartan takes a new Edge rendering engine while IE 11 keeps Trident — meaning every Windows 10 browser fix now has to be routed through two codebases instead of one.
- A distinct name and brand for Spartan under Capossela signals marketing will push the new browser to consumers, leaving IE to fade into an IT-managed utility rather than competing for default share.
Third-order effects
- If the pattern holds, legacy web compatibility becomes a managed add-on rather than the core browser — the structural template behind Edge shipping on all Windows 10 devices as the single branded front end, with the old engine demoted to an enterprise fallback.
- Enterprise dependence on old rendering engines becomes the pacing factor for how fast Microsoft can retire its legacy web stack, since each cleanup step must preserve an escape hatch for internal corporate sites.
The trend: Browser makers are separating their modern rendering engines from legacy compatibility modes, with enterprise lock-in to old web standards dictating how long the old stack survives inside the OS.