4 ms·

>> 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 Blue

>> 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.

troupo 9mo ago
> 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.
- kelthuzad 9mo ago
  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.
  - troupo 9mo ago
    > 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.
    - kelthuzad 9mo ago
      >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". There is nothing "funny" about me acknowledging facts, that's what a reasonable person should always do, try it. What's not funny though, is how you're butchering and misrepresenting my arguments to such a gross degree. I've never stated that everybody "must implement these non-standard features from Chrome", instead I've made a much more nuanced argument about how Apple's conflict of interest is motivating them to reject entire feature sets for competing technology instead of helping to implement a safe standard, which is indicative of their bad faith motivations. That anti-competitive strategy has been essential for Apple in collecting billions in app taxes by systematically hobbling any competition before it can emerge. >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. So? Just as native apps give users certain freedoms that can have problematic aspects, web apps should have _equal rights_ and be able to play on a level playing field. The choice and freedom should be the users' and not that of Apple's finance division. None of this gives Apple the right to uphold its anti-competitive strategy with its corporate double speak. And the fact that you're so hyperfocused on specifics while failing to grasp the broader argument, so you can cheerlead for Apple's anti-competitive behavior, is revealing a clear bias.
- xp84 9mo ago
  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.
  - troupo 9mo ago
    > 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/ https://mozilla.github.io/standards-positions/
    - leptons 9mo ago
      Firefox gets paid by Google. A lot. Maybe part of their agreement is to not implement some features because it would compete with Chrome. I don't really know, and I don't really care what Firefox does or doesn't do. I only care that Apple does not allow other browsers to use their own browser engines. Opera mobile also implements the APIs I need (on Android). Even MS Edge supports the APIs. Firefox can join Apple in being lame, I don't really care.
      - troupo 9mo ago
        "Every browser that doesn't jump when Google says 'jump' is driven by malicious actors and intent that I can't articulate beyond some tin-foil conspiracy theories" is not as good an argument as you think it is
        leptons 9mo ago
        I really don't care what browsers do or don't implement. I only care that Apple doesn't allow other browsers to use their own browser engines on iOS. That's it, that's all, and it also got notice from the DOJ, which is one of many reasons Apple is getting sued by the DOJ. Until Apple lets other browser engines on iOS, they are behaving like greedy tyrants.

troupo 9mo ago

> 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.

kelthuzad 9mo ago
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.
- troupo 9mo ago
  > 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.
  - kelthuzad 9mo ago
    >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". There is nothing "funny" about me acknowledging facts, that's what a reasonable person should always do, try it. What's not funny though, is how you're butchering and misrepresenting my arguments to such a gross degree. I've never stated that everybody "must implement these non-standard features from Chrome", instead I've made a much more nuanced argument about how Apple's conflict of interest is motivating them to reject entire feature sets for competing technology instead of helping to implement a safe standard, which is indicative of their bad faith motivations. That anti-competitive strategy has been essential for Apple in collecting billions in app taxes by systematically hobbling any competition before it can emerge. >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. So? Just as native apps give users certain freedoms that can have problematic aspects, web apps should have _equal rights_ and be able to play on a level playing field. The choice and freedom should be the users' and not that of Apple's finance division. None of this gives Apple the right to uphold its anti-competitive strategy with its corporate double speak. And the fact that you're so hyperfocused on specifics while failing to grasp the broader argument, so you can cheerlead for Apple's anti-competitive behavior, is revealing a clear bias.
xp84 9mo ago
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.
- troupo 9mo ago
  > 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/ https://mozilla.github.io/standards-positions/
  - leptons 9mo ago
    Firefox gets paid by Google. A lot. Maybe part of their agreement is to not implement some features because it would compete with Chrome. I don't really know, and I don't really care what Firefox does or doesn't do. I only care that Apple does not allow other browsers to use their own browser engines. Opera mobile also implements the APIs I need (on Android). Even MS Edge supports the APIs. Firefox can join Apple in being lame, I don't really care.
    - troupo 9mo ago
      "Every browser that doesn't jump when Google says 'jump' is driven by malicious actors and intent that I can't articulate beyond some tin-foil conspiracy theories" is not as good an argument as you think it is
      - leptons 9mo ago
        I really don't care what browsers do or don't implement. I only care that Apple doesn't allow other browsers to use their own browser engines on iOS. That's it, that's all, and it also got notice from the DOJ, which is one of many reasons Apple is getting sued by the DOJ. Until Apple lets other browser engines on iOS, they are behaving like greedy tyrants.