It has been argued with various success [1] that Chrome is the new I.E., due to "Chrome exclusive" web standards.
[0]: https://html5test.com/compare/browser/safari-11.2/chrome-30/...
Here is the correct comparison: https://html5test.com/compare/browser/safari-11.2/chrome-68/...
Which clearly shows its the worst of the bunch.
Edit: Also just noticed, the latest Chrome version that the site has is 68. We're currently on 80+
It's a weird world where webdevs apparently ideally just want everyone on the 6 second old version version of Chrome. I totally get it -- it's an absolutely rational stance but it feels a lot like how devs felt about IE6 at the beginning.
Plus because it's tied to the OS and the phone determines the maximum OS you end up with a bunch of users stuck on ancient and buggy versions.
This is to say nothing about the remote debugger purposefully locking you out of older versions for no reason to make debugging them harder.
A webview in iOS could sometimes crash system wide. Not enough to restart the app. You'd have to restart the device.
Felt like a sitcom when I had to ask customers if they'd tried turning it off and on again.
It's not even required or the default install on any OS. And it has rapid updates that constantly test new features and improve performance and security.
Any "exclusive" features are just early testing for later standardization. It's Safari that's lagging in implementing them.