Microsoft Edge Legacy

» see microsoft.com/edge as it lived, on the wayback machine

~ the obit ~

Edge Legacy shipped with Windows 10 on July 29, 2015. The pitch was that internet explorer had become a brand liability and Microsoft needed a new browser without the legacy compatibility hacks dragging it down. The team called the project Spartan during development, after the master chief armor in Halo, then renamed it Edge for the public launch. The engine was a fork of trident pared down to remove ActiveX and the older quirks. The javascript runtime was Chakra, also descended from internet explorer but rewritten for modern web workloads.

For a while Edge was actually fast. The benchmark numbers on the launch builds beat both Chrome and Firefox on most javascript suites, and Microsoft made a lot of noise about that. The browser had a real reading mode and a working pdf viewer, with Cortana wired into the address bar for voice search. The chrome was clean. Reviewers gave the launch genuinely warm coverage, which had not happened to a Microsoft browser in over a decade.

I used Edge Legacy on the windows 10 installs I kept around for office and gaming through 2015 to 2020. It was never the default I typed urls into. Chrome was already the muscle memory by then, and Edge always felt like the browser you got dropped into when you clicked a help link from inside windows. The download for Chrome stayed pinned on the taskbar. Edge stayed in the start menu where I never opened it.

~ the rap sheet ~

~ the rise ~

The first eighteen months were a real shot. Edge had genuinely faster javascript and lower power draw on laptops than Chrome did, plus tight integration with Cortana voice search. Microsoft poured advertising budget into Bing-and-Edge defaults across the windows 10 setup flow. The browser did not get to a meaningful share, but it did stop the bleed from IE without setting Microsoft on fire.

The extension story was supposed to be the moat. Microsoft promised that Chrome extensions would port to Edge with minimal changes, and a Microsoft Store catalog would curate the result. The catalog stayed thin. The porting was harder than advertised. The developer momentum kept flowing to Chrome.

~ the cracks ~

Web compatibility was the real problem. Sites tested in Chrome first and broke in Edge second. They stayed broken because nobody was filing bugs against Microsoft's bug tracker. The team at Microsoft kept catching up to web platform features that Chromium had already shipped. Every quarter the gap widened a little. By 2018 it was clear that maintaining a fully independent web engine was an open-ended commitment with no obvious revenue case for Microsoft.

In December 2018 Microsoft announced the rewrite. The new Edge would be built on the same Chromium project that Chrome was built on. The Spartan team kept the brand and the chrome along with the Windows integration, but threw away the rendering engine underneath. The reactions in the developer community ranged from relieved to sad, depending on whether you cared about engine diversity or about Edge actually working on web pages people built.

~ the postmortem ~

The new Chromium-based Edge shipped on January 15, 2020. Microsoft pushed it out to Windows 10 installs over the following year as a recommended update. Edge Legacy stopped receiving security updates on March 9, 2021, with the official end-of-support notice. By the end of 2021 it was effectively gone from the install base. Microsoft removed the EdgeHTML and Chakra source from public Github archives after the migration, leaving Chromium Edge as the only browser called Edge.

~ the inheritance ~

The engineering team did not vanish. A lot of the Edge Legacy work flowed upstream into Chromium itself, including PDF improvements and accessibility patches along with Windows-specific integration code. Microsoft is now one of the top contributors to the Chromium project. The independent web engines that survive in 2026 are basically Blink for the Chrome family and WebKit for Safari, with Gecko keeping Firefox alive as the third option. Edge Legacy's death is the moment the web rendering tier consolidated from four players to three. Browser monoculture got a step closer the day Microsoft gave up on having its own engine.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »