[troupo]

> Apple's conflict of interest is motivating them to reject entire feature sets for competing technology instead of helping to implement a safe standard

It literally is "everyone must immediately implement anything Chrome shits out". You don't even accept the fact that both Safari and Firefox team reject the entire premise on the same grounds.

Nope. "They must work on better standards for these features that Chrome ships".

> The choice and freedom should be the users' and not that of Apple's finance division.

Funny how in the paragraph you respond to I didn't mention Apple once.

> And the fact that you're so hyperfocused on specifics while failing to grasp the broader argument

There's no broader argument. You literally dismiss Firefox as irrelevant [1], assume that whatever Chrome ships is good, and assumes that Apple is both a bad actor driven entirely by money an must implement whatever Chrome comes up with (under the guise of "should work to implement a safe standard").

[1] Their position on these Chrome features is literally the same as Apple's https://mozilla.github.io/standards-positions/

[leptons]

It literally is "everyone must immediately not implement anything that cuts into Apple's bottom line"

Apple has veto power over what becomes web standards now. If they didn't abuse that power, and also forbid other browser engines on iOS, then there wouldn't be a problem. They abuse their power in a way that hurts everyone but Apple, and the DOJ took notice.

You say Firefox doesn't implement the same APIs that Apple won't as proof of something, but Opera and other browsers do implement those APIs, so that really cancells out whatever argument you thought you had.

Back in the day, Microsoft invented XMLHTTPRequest, and if Apple had veto power over web standards back then, the web might still be "Web 1.0", hypothetically speaking.

But now Apple can block progress in web browsers now, and the DOJ will likely prove that they are abusing their position to the detriment of everyone that uses a web browser, so Apple can make a few more dollars from their app store.

It should not be so difficult for anyone to understand.

[kelthuzad]

>It literally is "everyone must immediately implement anything Chrome shits out". You don't even accept the fact that both Safari and Firefox team reject the entire premise on the same grounds.

It isn't factually and certainly not "literally" that. I've explicitly stated that the problem isn't the rejection of the specific implementation in its current form, but the wholesale refusal of features to deny rival technology equal rights, instead of helping to implement a safe standard. That is evidence of Apple's bad faith motivation to hobble competing technology in favor of their App Store tax funnel. You consistently refuse to understand this and resort to deflecting from and distorting that fact.

>There's no broader argument.

There is, it's the one you've been deflecting and distracting from, because it refutes your biased talking points completely.

>You literally dismiss Firefox as irrelevant [1][1] Their position on these Chrome features is literally the same as Apple's https://mozilla.github.io/standards-positions/

No I don't. You're literally making stuff up and ignoring the fact that I have actually even started my response with an acknowledgement of that point: "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." https://news.ycombinator.com/item?id=46457938

>and assumes that Apple is both a bad actor driven entirely by money an must implement whatever Chrome comes up with

There is no such assumption, only the fact that Apple has a conflict of interest, which manifests itself in anti-competitive behavior, for which I've provided documented evidence. I've also never stated that they "must implement whatever Chrome comes up with", that's a gross misrepresentation, which you are stubbornly repeating, despite me having refuted it several times now. Your bias in this matter couldn't be more obvious, due to your dedication to distorting any evidence that refutes Apple's propaganda narrative, so you keep blindly repeating the same tired and old talking points despite evidence to the contrary.

[troupo]

> You're literally making stuff up and ignoring the fact that I have actually even started my response with an acknowledgement of that point: "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

Rule of the thumb is "nothing you say before 'but' matters". Apple's opposition to Chrome features is not just echoed by Mozilla. It is repeated almost verbatim.

And yet, you completely ignore all that, and go to say "well, Apple is bad, and conflict interest, so Apple must work on a better safe standard for these features". You don't even for a second assume that two of the three browser vendors oppose these features for the same reason. No. Chrome shipped them, so they absolutely must work to implement these features (in some form) because Apple bad or something.

> There is no such assumption,

"the wholesale refusal of features to deny rival technology equal rights, instead of helping to implement a safe standard." Yup. "Whatever Chrome ships must be implemented no matter the cost and despite any opposition for any reason".

> only the fact that Apple has a conflict of interest, which manifests itself in anti-competitive behavior

Which literally has nothing to do with Chrome-only non-standards. Chrome wants them. It's on Chrome to design and implement them safely. Neither Apple nor Mozilla owe them anything regardless of the amount of demagoguery around their decisions. Both Apple and Safari pointed out the issues they have across many discussions. Chrome didn't care.

Safari has multiple issues, that's true. None of them stem from refusing to support every shitty thing that Chrome vomits into the world and calls a standard.

Speaking of "denying rival technology equal rights". Do you know that WebSQL was implemented by Chrome and had approval from Safari, but got killed due to opposition from Mozilla? Did Mozilla "deny rival technology equal rights"? Or perhaps, just perhaps, they had valid concerns that lead to rethinking of the approach?

You can't even come up with proper rebuttal of Mozilla's and Apple's concerns (you don't even know about their concerns to begin with) beyond "but native apps" and diatribes about Apple.

BTW here's Mozilla relenting on just one of the hardware APIs: https://news.ycombinator.com/item?id=33995022 (sadly, the twitter account has been locked)/ Original quote: "Just a day after shipping an impl to Firefox Nightly, this is the first discovered case of WebMIDI-fingerprinting... Chrome still allows web developers to enumerate attached MIDI devices without user consent or even a notification, btw."

[kelthuzad]

[flagged]