The problem isn't the the number of APIs per se (though I agree that it's unsustainable [1][2]).
It's how they get forced onto the web by Chrome.
- Implementing Chrome's internal API and pushing them to stable, and pretending they are a web standard? Check (Example: Web HID, original "spec" couldn't be understood by Mozilla engineers, updated "spec" was published two months after Chrome enabled it by default and published an article on web.dev)
- Ignoring Mozilla and Safari concerns on an API, enabling in stable because Google's own projects want them, and refusing to bring it back under flag? Check (Constructible Stylesheets, in the end Safari refused to implement them, period)
- Gaslighting other browser vendors through any means possible to an audience of thousands? Check (Alex Russel and the likes of him)
And that's off the top of me head, too late here where I am going through dozens and dozens of such instances I saved to document in a blog post one day.
> It's sad that it's got the point where the teams don't trust each other and it's clear that the perception is wider. I'm still hoping to change that around.
I will quote John Nightingale [3]
--- start quote ---
The question is not whether individual sidewalk labs people have pure motives. I know some of them, just like I know plenty on the Chrome team. They’re great people. But focus on the behaviour of the organism as a whole. At the macro level, google/alphabet is very intentional.
--- end quote ---
All this is very intentional behaviour that has been going on for years. No wonder Safari team is pissed.
[1] https://www.quirksmode.org/blog/archives/2015/07/stop_pushin...
[2] https://drewdevault.com/2020/03/18/Reckless-limitless-scope....