[troupo]

> Given that Chrome isn't shipping ActiveX or Flash, what's the issue?

What does this have to do with what I wrote? Literally nothing

> Apple and Mozilla decide how (or if) they want to implement each standard.

For something to become a standard there needs to be consensus, and at least two independent implementations.

Just because Chrome ships something doesn't make it a standard.

> If there's no demand for the feature, it shouldn't be a problem ignoring it. If icky features like WebUSB and Bluetooth are terrible, users won't notice anyways.

Neither WebUSB nor Bluetooth are standards. There status is literally, and I quote, "It is not a W3C Standard nor is it on the W3C Standards Track. "

> Google's strategy is pressuring Apple to make more capable software.

That's not Google's strategy, and never has been. It's also quite telling you decided to ignore Google's clear anti competitive practices. I guess by sabotaging Firefox they were also "pressuring Firefox into making more capable software or something".

It amazes me to no end that Apple/Safari haters will contort themselves to no end to justify Google because Chrome can do no wrong.

> When a user has more freedom in a browser than they do in their hardware's native runtime

Google couldn't care less about the end user. All Google cares about is its dominance. To that end it doesn't care if it breaks the web [1], or twists it to their liking [2]

[1] Speaking of breaking: Breaking the Web forward https://www.quirksmode.org/blog/archives/2021/08/breaking_th... and Stay Alert https://dev.to/richharris/stay-alert-d but you will ignore these, too. Because it's not "ActiveX or Flash", innit?

[2] People keep mentioning sites like https://whatwebcando.today/ and https://whatpwacando.today/ and they are filled to the brim with APIs that Chrome ships and whose status is "not on any standards track".

[smoldesu]

> What does this have to do with what I wrote?

Everything, really. ActiveX and Flash were proprietary runtimes, which is a real example of a domination play. To my knowledge, Chromium doesn't feature anything that couldn't be reverse-engineered or conditionally re-implimented by third-parties. Maybe some things are nonstandard, but if there's user demand for it then why complain? The native iOS runtime clearly isn't making everyone happy.

> I guess by sabotaging Firefox they were also "pressuring Firefox into making more capable software or something".

Nobody but you has been talking about Chrome's anticompetitive practices in this thread. I might actually agree with you, but I'm not going to discuss it because it's tangential to Apple's own anticompetitive practice.

> Google couldn't care less about the end user. All Google cares about is its dominance.

I'd have an easier time believing you if I couldn't use the web with my Open Source browser.

> but you will ignore these, too.

Both of those posts are actually valid complaints, and they're just as valid when the breakage is on Safari's side. Much as you'd rather minimize it, "who owns the web" is also a valid question when leveled against Apple too.

[troupo]

> Everything, really.

Nothing at all, really

> To my knowledge, Chromium doesn't feature anything that couldn't be reverse-engineered or conditionally re-implimented by third-parties.

To your knowledge. It's just Chrome-only Chrome-specific code inside a 50-million-line codebase that may or may not depend on very Chrome-specific things.

> Maybe some things are nonstandard, but if there's user demand for it then why complain?

Because you've just literally supplanted standards processes with "whatever Chrome ships is standard now". Are you even aware that Chrome ships 400 new web APIs a year?

> Nobody but you has been talking about Chrome's anticompetitive practices in this thread.

Indeed. Very few people talk about Chrome's practices, period. You could look up the thread why I started talking about Chrome's practices.

> I'd have an easier time believing you if I couldn't use the web with my Open Source browser.

Ah yes. The only thing that's needed for a company doing whatever the hell it wants is to provide the source. Who cares if no one has any say on what gets implemented in that browser. Who cares if even that company admits that no one contributes to that browser: https://twitter.com/RickByers/status/1715568535731155100

I mean, you could use the web with internet Explorer, too, so why complain?

And yes, there's an increasing number of sites (including sites from Google) that carry the "only works in Chrome" or equivalent banner. So no, increasingly I cannot use the web using an open-source browser of my choice.

> Much as you'd rather minimize it, "who owns the web" is also a valid question when leveled against Apple too.

I don't minimize it. I point out the one-sidedness of the judgments leveled against Apple.

[smoldesu]

This thread isn't about the one-sidedness of Apple's criticism. It's about criticizing Apple, and you're deciding to derail it with an unrelated strawman arguement.

If you want to circle back around to the point, I'm glad to keep discussing it.

[troupo]

This is the comment I was replying to in this thread: https://news.ycombinator.com/item?id=39408640 Where the person quite literally said "I don't care if it only works in Chrome, since its market share is high enough".

[smoldesu]

And then the second sentence following that is: "I don’t think Apple can tell alternative browser engines what features it will allow and which not."

The core problem is not Chrome's adoption of random features. It's Apple's neglect of the native platform, which in turn creates demand for absurd workarounds. As I said way further up in the thread, they're not pushing proprietary browser extensions; so how is it anticompetitive?

[fifafu]

I replied to a post asking „And if PWA were such a threat to Apple's business then why are they allowed in US.“

Whether Web Bluetooth, Web HID etc should be implemented in a browser engine is really irrelevant in this context - but the thing is they CAN be implemented in a browser engine. So can pretty much any native functionality currently guarded by the App Store.