What does this have to do with what I wrote? Literally nothing
> Apple and Mozilla decide how (or if) they want to implement each standard.
For something to become a standard there needs to be consensus, and at least two independent implementations.
Just because Chrome ships something doesn't make it a standard.
> If there's no demand for the feature, it shouldn't be a problem ignoring it. If icky features like WebUSB and Bluetooth are terrible, users won't notice anyways.
Neither WebUSB nor Bluetooth are standards. There status is literally, and I quote, "It is not a W3C Standard nor is it on the W3C Standards Track. "
> Google's strategy is pressuring Apple to make more capable software.
That's not Google's strategy, and never has been. It's also quite telling you decided to ignore Google's clear anti competitive practices. I guess by sabotaging Firefox they were also "pressuring Firefox into making more capable software or something".
It amazes me to no end that Apple/Safari haters will contort themselves to no end to justify Google because Chrome can do no wrong.
> When a user has more freedom in a browser than they do in their hardware's native runtime
Google couldn't care less about the end user. All Google cares about is its dominance. To that end it doesn't care if it breaks the web [1], or twists it to their liking [2]
[1] Speaking of breaking: Breaking the Web forward https://www.quirksmode.org/blog/archives/2021/08/breaking_th... and Stay Alert https://dev.to/richharris/stay-alert-d but you will ignore these, too. Because it's not "ActiveX or Flash", innit?
[2] People keep mentioning sites like https://whatwebcando.today/ and https://whatpwacando.today/ and they are filled to the brim with APIs that Chrome ships and whose status is "not on any standards track".