That only reveals a lack understanding how IE 5 took over the Web world.

It slowed down when it won, same will happen to Chrome after Google is done turning it into ChromeOS.

Safari is the only relevant browser preventing Google to achieve that goal.

On release, IE6 was so ahead on CSS standards conformance it broke websites. The old (long-forgotten) incantation for accessing XMLHttpRequest is the way you create a COM IDispatchEx object by ProgID from inside Active Scripting, because that was the way it worked in the original IE implementation. Before there were PWAs or Electron, there was the HTA, introduced with IE5. (Admittedly XUL came even earlier.) And so on—those are not exceptions.

It’s just that once Microsoft won the web, it turned out what they wanted to do with it as the main competitor to their fat-client business was nothing, so the IE team was effectively dissolved and IE stagnated, leaving an opportunity for Firefox to displace it. But before that happened, they innovated like crazy, up to and including (by some accounts) a right to demand features they needed from the Windows team—and, on the other hand, writing the original implementations for others: multilingual UI, a Unicode layer for 9x, windowless ActiveX controls, new revisions of the common controls, etc.

So you’re right that Chrome is not the new IE of 2009: Chrome is the new IE of 1999. And unlike Microsoft back then, Google now seem perfectly happy to fund the hamster wheel if it means every other prospective browser is also forced to run inside it or lose users.

> That sounds overly dramatic

Try appending this piece of code to your `index.js` and let me know how it goes in Safari:

    const r = /(<!foo)/

The parser will encounter a syntax error and no code is executed.