Comment by kelthuzad
9 days ago
>> And Apple purposely will never implement lots of APIs that only their native apps allow (which other browsers implement)
>Can you give an example?
Web Bluetooth, Web USB, Web NFC, Web Serial...
Of course Apple will uphold its usual charade to claim that it's about pRiVacy & sEcuRiTy to maintain plausible deniability. They could easily implement it and keep it disabled by default, such that users could make the conscious choice to enable it or keep it disabled. Any adequate analysis of Apple's behavior and motivations must mention Apple's conflict of interest, because Apple will be biased against technology that could diminish the value proposition of "native" apps which Apple has been taxing so unchallenged for all these years.
> Web Bluetooth, Web USB, Web NFC, Web Serial
Chrome-only non-standards. Note that Firefox is against these, too.
> Any adequate analysis of Apple's behavior and motivations must mention Apple's conflict of interest
I've yet to see an adequate analysis that doesn't pretend that anything Chrome shits, sorry, ships is immediately a standard that must absolutely be implemented by everyone immediately.
You're right that Firefox also opposes some of these specific implementations in its current form, and that Google often rushes features. However, that doesn't diminish Apple's conflict of interest at all, so sometimes their arguments happen to align with reality just as a broken clock is correct twice a day. Apple applies many double standards e.g. they allow native apps to access these hardware features (where they happen to collect a 30% tax) but block the Web from doing the same (where they collect 0%). If privacy was the only concern, they would work on a safe standard, but instead they block the capability entirely to ensure that any of the App Store's rivals remain constrained and thus inferior such that the App Store's revenue isn't threatened.
> You're right that Firefox also opposes some of these specific implementations in its current form, and that Google often rushes features. However, that doesn't diminish Apple's conflict of interest at all
Funny how you agree that Firefox opposes these non-standards, and how Google rushes things. And immediately turn around and basically say "no-no-no, Apple is to blame and Safari (and, by extension Firefox) must absolutely implement these non-standard features from Chrome".
The rest of demagoguery is irrelevant.
BTW literally the moment Firefox relented and implemented WebMIDI they had originally opposed, they immediately ran into tracking/fingerprinting attempts using WebMIDI that Chrome just couldn't care less about.
6 replies →
Are the Chrome features useful? Are they open? If it’s bad for users (e.g. some new ad tracking) or if it’s proprietary and thus expensive to license or reverse engineer that’s one thing, but if it’s not that, then refusing to ever adopt those standards (or to provide their own alternatives) is either foolish NIH syndrome on Apple’s part or it’s greed.
> If it’s bad for users (e.g. some new ad tracking)
Yes
> but if it’s not that, then refusing to ever adopt those standards (or to provide their own alternatives) is either foolish NIH syndrome on Apple’s part or it’s greed.
Note that Firefox's position is literally exactly the same as Apple's on these Chrome-only features: https://mozilla.github.io/standards-positions/
22 replies →