> You are complaining about a problem that nobody is facing.
Nobody is facing yet.
That is my point. It's a huge danger that people aren't appreciating enough. If we want to use the history of IE as a warning lesson lest we are dumb enough to repeat it, it's a warning on letting a single browser get too much marketshare. It's a warning on relying on "bleeding edge" features that aren't yet stable.
It feels like the problem is "all these other browsers are buggy and outdated", but that isn't the danger, that's the symptom of the danger. People said the same thing about Netscape/Pheonix/Firefox when IE was "winning" that those browsers were too slow and "preventing the web platform from being useful". That's the dangerous cycle here.
Maybe we'll be extremely lucky and the Chrome hegemony will never be the same problem that IE was. But blaming Safari for being "slow" in this scenario is putting the blame on the victim of the hegemony problem.
And nobody ever faced with IE. That wasn't the problem with IE. That is my point.
> It's a warning on relying on "bleeding edge" features that aren't yet stable.
MSE isn't bleeding edge or unstable. Apple itself implemented it years ago on Safari for Mac, where it has no App Store revenue to protect.
The feature this article is about isn't bleeding edge or unstable either. Apple is implementing it exactly the same way all the other browsers already have.
Nobody is facing yet.
That is my point. It's a huge danger that people aren't appreciating enough. If we want to use the history of IE as a warning lesson lest we are dumb enough to repeat it, it's a warning on letting a single browser get too much marketshare. It's a warning on relying on "bleeding edge" features that aren't yet stable.
It feels like the problem is "all these other browsers are buggy and outdated", but that isn't the danger, that's the symptom of the danger. People said the same thing about Netscape/Pheonix/Firefox when IE was "winning" that those browsers were too slow and "preventing the web platform from being useful". That's the dangerous cycle here.
Maybe we'll be extremely lucky and the Chrome hegemony will never be the same problem that IE was. But blaming Safari for being "slow" in this scenario is putting the blame on the victim of the hegemony problem.