@mitch The tragedy in both instances is that the teams that dropped turds in Chrome have faced no pressure to move to open, interoperable APIs, meaning other browsers (including other Chromium ecosystem browsers) feel forced to include them to make sure that Google's very popular web properties "work right".

This also keeps web APIs from advancing because teams that would push them forward already have theirs, Jack. It's not Android levels of bad, but it's bad.