alt Hacker News>The very important part about this is whether or not these features are actually considered a web standard or is it Google pushing their own agenda.
Apple is on the W3C board that gets to decide what APIs become standards, so Apple is definitely pushing their own agenda on the W3C.
So you can't really complain that Google is pushing their own agenda with these APIs when Apple is the one refusing to make them a standard. In this case, Apple is the one doing shady shit by holding back things like web bluetooth for no good reason. No, "security" is not a reason, this API has been in use on other platforms for a very long time with no real security issues.
There are lots of other standard APIs that have been implemented, but Apple refused to let the ones that eat into their app store go forward.
>we heavily criticized IE for exactly this and yet we celebrate Chrome for it?
I remember when IE implemented XMLHTTPRequest, and it did a lot of good for the web.
I also remember when Microsoft got an antitrust case for simply bundling IE with Windows, yet Apple seems to get a pass for forbidding all other browser engines on iOS? Well, fortunately Apple has its own antitrust case in the DOJ now for its own abusive business tactics.
https://www.justice.gov/archives/opa/media/1344546/dl?inline
Google is also involved in W3C and do I really need to bring up the topics API as Google attempting to use their position to push their agenda as well?
We really need to stop putting google on a pedestal as if they are truelly on the side of an open web, like every company they are looking out for their own interests. Which is fine, they are allowed to do this.
That doesn't change that many of these are in fact not a standard according to W3C and should not be implemented in any browser until it is. A discussion about why it may not be standard is worth it, but that is also a very important distinction that is not made on this page. Right now it is framing it as google supports a standard that the other's (including Firefox) do not.
Just because Google does something it doesn't mean the rest of the industry should follow. If we did that in IE days we would still have ActiveX