4 ms·
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 "EE
by nwienert 1y ago
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&compareCats=all 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 1y agoMaybe 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 1y agoSo you’re ignoring my entire comment and re-iterating the part I didn’t respond to.
- leptons 1y agoNothing 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 1y agoSafari 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 1y agotechnically?? 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 1y agoI linked to my source, I think you haven’t updated your priors in >5 years or so.
- leptons 1y agoApple sez: We don't want to implement any of those APIs, and we forbid you to use a browser that implements them, because reasons. Your comments are some Stockholm-syndrome level nonsense you're spouting to protect your favorite brand.
- nwienert 1y agoWhich API's did they not implement? I really never commented on lock-in, even said it's fine to dislike it. You're fighting an imaginary opponent here. I really just pointed out that Safari largely caught up on web standards. It's Google doing the whole "embrace, extend, extinguish" thing that IE pioneered by stuffing non-standards into their browser so they can lock people in.
- leptons 1y ago>It's Apple doing the whole "extinguish" thing that Apple pioneered by forbidding other browsers so they can lock people in FTFY Without IE we wouldn't have XMLHTTPRequest, something used by practically every web developer in existence today. Innovation happens, and apparently so do walled gardens that outright forbid any competition. It's one thing to not implement web bluetooth, web midi, and other APIs on your own browser, it's quite another to block anyone else from doing so with their web browsers. The EU thought so too and forced Apple to let other browsers use their own engines. But not in the US yet, until the DOJ completes the case against Apple.