Safari is a terrible, Apple-like version of WebKit. The last viable windows version of Safari was abandoned 8 years ago, so please nobody use this browser.
Chrome is slower and Firefox on mobile is a joke.
When I was working more frontend (~1,5 years ago) no browser would cause more work and trouble for us than Safari on iOS (we didn't have to support IE9 and lower).
Also I understand that Safari might've created some pain for you as a frontend developer, but frankly I don't care. I'm an end user and I only care about how fast and secure the browser is. And Safari wins there, it's not terrible by any measure for the end user.
Development wise it's not so much about our pain as about certain known bugs that went unfixed for up to 2+ years, similar goes for a range of CVEs (re:being secure).
I realize that this is subjective, but Firefox Focus has been my preferred mobile browser, regardless of if I have Safari available, (iPad), or not, (Android). In fact having desktop addons on Android has been great.
A couple issues with Safari I've seen since it's slower to adopt web standards:
- buggier websites from devs who don't have iPhones. Since there are some quirky inconsistencies with how webkit handles css vs other browser rendering engines it's easy not to catch those quirks if you don't have an iPhone to check them with. And once users point them out, it's a pain to fix without a physical device.
- a smaller web feature set than chrome/Firefox. For instance, Safari doesn't allow localstorage while in incognito. I think it supports serviceworkers and webrtc now but it took years to get them.
Isn't that good for privacy? Localstorage can store unique IDs and other data about the client's past behavior, it's much more dangerous than cookies.
Websites can detect the absence of localstorage and change their behavior, e.g. notify the user that information will be lost after the session ends.
It does allow (at least in the version I'm using), but doesn't persist the data between sessions. Which is the whole point of Icognito mode.
Why is that so unbelievable? I use Firefox every day and haven't even considered that this might be a problem. I don't have difficulty hitting the [-] on HN, but if I did, I would simply zoom in until it becomes large enough.
Chrome still had a slightly better UI the last time I tried it but the gap wasn't remotely wide enough to give up ublock origin.
Adverts are even more annoying on phones than they are on desktop so been able to run ublock origin directly on device is a major win.
Here's an example that broke many many sites that use OAuth2 Auth Code Flow for login (including the main UI portal my company provides clients): https://bugs.webkit.org/show_bug.cgi?id=194906
There's also been issues with the handling of 3rd party cookies that create issues for login systems, js stdlib functions being incorrectly implemented, etc.
Chrome generally implements everything new and shiny, no matter how underspecified it is, and with blatant disregard to whether or not it breaks the web.
Software has these everywhere. iOS and Android homescreens are carousels. Netflix 'rails' are carousels. CSS Snap Points is a way to create native snapping scrolling views, which Safari and IE supports, but Chrome does not.
(But yes, if I do Frontend development, I use Chrome)
It supports the same crippled ad blocking that this article complains about. It is also years behind the competitors in standards support, and the standards it claims to support are implemented buggily. Finally, it crashes more often than its competitors, but I suppose making a browser unusable is one way to save battery.