[nwienert]

Maybe 5 years ago this was a true, they accelerated development and their standards support is pretty good now, better than FF. Again, not counting Chrome's "EEE" non-standard API's, they largely move fast and implement most modern ones. Some PWA stuff is missing which is valid, while Chrome is behind on a few nice design-focused standards Safari has.

Go here:

https://caniuse.com/?compare=chrome+143,safari+26.0&compareC...

Note the non-supported Safari API's, the vast majority are not web standards.

[leptons]

Maybe you should read the DOJ suit against Apple. It's pretty clear that one reason (among many) that Apple is getting sued is because of abusive business practices exactly as I described.

Apple forcing Safari on iOS is present day, today, not 5 years ago (but it was also 5 years ago too, ever since there was an iOS webview). If Apple doesn't want to implement it, then they shouldn't force other browser makers to use their hobbled browser engine.

[nwienert]

So you’re ignoring my entire comment and re-iterating the part I didn’t respond to.

[leptons]

Nothing in your comment makes any difference so long as Apple blocks other browser engines on iOS. I honestly don't give a fuck what they do with Safari as long as they allow real Chrome to exist on iOS, which I can then instruct my users to install because Safari is a piece of shit browser.

[nwienert]

Safari is better than Chrome imo, technically, UX and otherwise, but you're entitled to be mad about lock-in. I just wasn't responding to that part.

[leptons]

technically?? With all those modern and useful APIs they don't implement? That's how they're technically better by not having useful tech? Wow. Okay, you do you.

[nwienert]

I linked to my source, I think you haven’t updated your priors in >5 years or so.