This thread isn't about the one-sidedness of Apple's criticism. It's about criticizing Apple, and you're deciding to derail it with an unrelated strawman arguement.
If you want to circle back around to the point, I'm glad to keep discussing it.
If you want to circle back around to the point, I'm glad to keep discussing it.
The core problem is not Chrome's adoption of random features. It's Apple's neglect of the native platform, which in turn creates demand for absurd workarounds. As I said way further up in the thread, they're not pushing proprietary browser extensions; so how is it anticompetitive?
Whether Web Bluetooth, Web HID etc should be implemented in a browser engine is really irrelevant in this context - but the thing is they CAN be implemented in a browser engine. So can pretty much any native functionality currently guarded by the App Store.