undefined

points

[-]

If web developers stop ensuring their sites work in Safari, their sites will still work in Safari because Google ratifies and publishes the web standards that Chrome follows so that Safari and other browsers can follow it too, something that Safari actually does less than Chrome.

Consumers choosing Android isn't a choice of which browser to use, it's choosing which operating system to use. That doesn't sound like you care that consumers get to choose which browser they use, that's letting Apple choose which browser that Apple consumers use then telling them they can choose a different operating system instead.

by bigyabai1 hours ago|

prev|

[-]

It's a chicken-and-egg problem. How can you get web developers to test their websites in Safari, when the majority of Mac devs haven't opened Safari in ages? We have the answer already. Safari doesn't compete on it's own merit.

WebKit is a second-class citizen on the web, and we can argue about why that is, but nobody can sincerely deny it. Apple's strategy has been dead in the water for over a decade. iOS lost.

by simondotau1 hours ago|

parent|

[-]

Safari is still relevant and iOS hasn't lost; the very existence of this thread serves as a clear rejection of that framing. If Safari wasn't competing, or if iOS had lost, nobody would care.

Meanwhile we have people bitching and moaning and meanwhile, as a Firefox user, I go to Safari when I encounter a website that doesn't work in Firefox. Because at the end of the day, developers are forced to test in Safari, and that is a Good Thing. No developer is forced to test in Firefox.

by leptons45 minutes ago|

parent|

[-]

>the very existence of this thread serves as a clear rejection of that framing.

The existence of the "Switch to Safari" campaign is a clear rejection that Safari is competing - it's not, it's the laughing stock of web browsers in 2026, it holds the same place that IE6 did in the early 2000s.

>Because at the end of the day, developers are forced to test in Safari,

I'm not forced to test in Safari, because I don't have money for an iOS device. So Apple users can continue to suffer with whatever browser they use on their i-device. I really don't care, and Apple has done this - not me, because they offer no way but purchasing their hardware to test their wonky browser engine.

And yes, you can emulate an android device on MacOS, so don't bother trying that again. You don't need to purchase an android device to test on android.