Earlier quoted context omitted.
You’re holding on too tight to an argument for the sake of analogy. It’s cute and evocative but it’s blinding you to the bigger picture. The issues with Google monopolising the direction of standards development are the major issue facing browsers, users and developers on the web, today. I get that you’re disappointed Safari doesn’t support the same stuff, the same way as Chrome. Tough. You’re attempting to develop a…
That's absurd. I'm not targetting Lynx, Haiku, or 8 year old shitty phones. Nor are most web developers. And the attitude that you must support those things is detrimental to the web. It makes people feel like they're doing it wrong of they don't spend all their time chasing those rare edge cases. Which if you're trying to start something new, can kill your productivity. I'd rather have web developers target the comm…
I’m not against browsers having features. They can add whatever they want. Devs can target them too.
But “the web”, the platform, the standards process, the language specs, the method of their development is all about maintaining access for the widest range of users for the longest time possible. Or it was. There’s nothing about it stopping you from restricting your own market to support users and devices you want to support… but insisting all mainstream browsers support all the brandest-newest features because ONE of them added it does a disservice to the platform.