Which makes Google Chrome a modern day IE. They push basically proprietary nonsense into the web that eventually gets scrapped or forced into being an open spec at which point its harder to redefine since it became a "works on my browser" implementation.

Except that the problem with IE was stagnation in era of IE6, not new standards backed by patent free and open source libraries.

The original problem with IE was its implementation of early CSS drafts - an open standard with specs. They just picked the “wrong” version of such specs and pushed it with their commercial strength. Everyone else was then caught between the choice of implementing the real (better) spec, or lose compatibility with IE.

Similarly, Google now picks the standards it likes, and everyone else is caught between the choice of investing in those or lose compatibility with Chrome. Not much of a difference.

I feel that Safari (mobile one) is way closer to the IE6 status with its ban of competition on platform, lack of standardised features and heavy handed management.

You can easily replace Chrome, it's not even a platform default. You're forbidden from replacing Safari.

I'm not sure why you're voted down. Mobile Safari has thrown some really bizarre and awful bugs at a few projects I've worked on, and given how critical mobile experiences are these days, it's genuinely a pain in the ass. It's a very nice mobile browser for the most part, but what it gets wrong is enough to make me kind of loathe having to deal with it.

I had thought that Chrome's Blink engine was the platform default on Android. But I am not sure.

How does a web developer test for Android compatibility? I have been testing against Chrome only.

Chrome on iOS is just wrapper around safari WebKit.