Having a more diverse team working on Chromium makes stagnation less likely, and the diversity should encourage innovation as the open source project works to support more needs and takes on board more code. Microsoft will also bring some of its expertise to areas like touch and scrolling, where Chromium doesn’t perform as well as Edge. Microsoft has said that it’s going to be a big part of the Chromium open source community, and its developers have already been contributing to the ARM64 branch of the project. While that does mean one fewer browser rendering engine for developers to accommodate, and a tilt of the balance of the web in favor of Chromium, we’re not looking at a repeat of the IE6 monoculture. Despite efforts to regain the browser dominance Internet Explorer once had, Now Microsoft has looked at its telemetry and seen that how web applications are being built means it needs to switch to using Google’s open source Chromium project and its Blink HTML and V8 JavaScript engines in the next major release of Windows’s Edge browser.īringing its browser to where the developers are makes sense for today’s more-pragmatic Microsoft.

That’s more than 23 years of first a variant of the Spry engine, then Microsoft’s own Trident, and finally, with the launch of Windows 10, EdgeHTML. Windows has had its own HTML rendering engine since the launch of the first Internet Explorer, back in 1995. Microsoft’s seismic shift from its own browser engine to Google’s Chromium for Windows’s Microsoft Edge browser is one of the biggest changes to the Windows platform in a long time.

Chromium browser engine