> Apple purposely won't implement some APIs so they can force developers to create an app for their app store where they can collect money from any additional sales through the app.
So then why doesn't Firefox support the Web Bluetooth API either? How can you jump to the conclusion that the lack of Safari support is about apps?
The reality is that the Web Bluetooth API is a draft. Not ratified. Not on the formal standards track. And Firefox doesn't even intend to implement it, due to security and privacy concerns around it and the fact that is it not ratified.
But go on assuming it's all about being anticompetitive...
> It's all spelled out in the DOJ suit, why won't you just read it?
I just did a Ctrl+F for Bluetooth and everything relates to smartwatches, not web APIs. There are only two references to Safari, none of which say anything about standards. The phrase "web standard" appears nowhere. The document is 88 pages long, and it's not immediately obvious to me where any of what you're talking about is spelled out. I hope you'll understand I'm not going to spend my afternoon reading the whole thing.
I don't really care what Firefox does. They get paid massively by Google, so who knows what their motivations are for what they do. Opera implements the same APIs in their browser, but that also doesn't work on iOS because Apple are dicks and force Safari on Opera too.
>Not on the formal standards track.
What a coincidence, Apple gets to vote on what the "formal standards track" is, and they have voted against anything that would hurt their app business.
>But go on assuming it's all about being anticompetitive...
Okay... Apple are anticompetitive and always have been. They forbid their OS from being installed on any hardware that isn't manufactured by Apple, even though it was easily possible to do. Their walled garden is very famous for being anticompetitive - banning any browser from using their own browser engine and forcing Safari is absolutely anti-competitive.
You know what? Just go fucking read the DOJ antitrust suit against Apple, it details the very many ways Apple is anti-competitive:
You seem to have lost the plot here. I started out by saying Apple is anticompetitive in plenty of areas.
But that's not what the conversation is about. I pointed out that in this area, it doesn't appear to be.
So I don't know why you keep pushing this PDF. It doesn't say anything about this specific area. I already checked.
And if you don't care about what Firefox does, then I think it's clear you're not having this conversation in good faith. You're not open to evidence or counter-argument, you just have a knee-jerk reaction that Apple is bad. OK, you do you. But I'm not going to waste any more time with someone who "doesn't care" about the most obvious counterpoint to their argument.
Unfortunately, many people here don’t enter the arena with open minds. Their opinions have congealed; there are good guys and bad guys; and they just want to rant and complain. They don’t want any solutions other than their preferred one.
What the hell? This is a completely unacceptable comment on HN. This is a discussion about Apple and browser engines. We've had to ask you before to observe the guidelines, and we have to ban accounts that continue to post abusive comments. HN is only a place where people want to participate because others make the effort to raise the standards rather than dragging them down. Please start acting like you want this to continue to be a place for worthwhile discussions.
So then why doesn't Firefox support the Web Bluetooth API either? How can you jump to the conclusion that the lack of Safari support is about apps?
The reality is that the Web Bluetooth API is a draft. Not ratified. Not on the formal standards track. And Firefox doesn't even intend to implement it, due to security and privacy concerns around it and the fact that is it not ratified.
But go on assuming it's all about being anticompetitive...
> It's all spelled out in the DOJ suit, why won't you just read it?
I just did a Ctrl+F for Bluetooth and everything relates to smartwatches, not web APIs. There are only two references to Safari, none of which say anything about standards. The phrase "web standard" appears nowhere. The document is 88 pages long, and it's not immediately obvious to me where any of what you're talking about is spelled out. I hope you'll understand I'm not going to spend my afternoon reading the whole thing.