The difference between the resources Google and Apple contribute to their respective open source browser engines is night and day, and as any web developer will know - it shows.
In an ideal world two things would change at the same time: Apple is forced to allow other browsers, and webkit gets some genuine love and decent resources to make it a legitimate competitor again, instead of being used as a pawn in a game between Apple and Google.
Google pushes out yet another half-baked, poorly considered new feature in Chrome and overnight has mobs chanting about Safari purportedly holding everyone back because of some close to irrelevant fringe thing.
Safari might just be the fastest browser, and it supports a ridiculous, awe-inspiring array of features and standards.
And the greatest indictment of the ridiculous anti-Safari smear is that no platform uses the browser more than iOS users do. iOS users always are over-represented in web usage compared to marketshare.
Arguably it’s a result of having no competition on iOS.
From idb, webrtc, to scroll to viewheight, to performance issues Safari is the worst to deal with and this is reflected in all the developer surveys.
This is a bit like saying India has the smallest number of people in countries named China or India.
It's still an enormous number of features, and it is simply extraordinary what is capable in the browser.
"this is reflected in all the developer surveys"
Remember "Made for IE"? IE was dogshit, yet there were loads of devs who thought ActiveX was the bee's knees and having to deal with other browsers and platforms was just an annoyance in their lives.
Developer surveys on this are worthless, and if we listened to developers as a group it would be an entirely Windows world.
I don't think that's true.
There were loads of devs that thought that ActiveX was the quickest route to the best experiences for the largest market segment and having to deal with other browsers and platforms was something the people signing paychecks cared less about, if at all.
Many developers would prefer a single, universal browser. A single platform. A single input mechanism (a single development language, compiler, RDBMS, filesystem, cloud provider, backup system, etc). All for obvious, practical reasons, at least in the short term.
That would be devastating for the future, but if it makes projects easier today, many developers are entirely onboard.
That was very much a dominant position among developers in the IE days. Other browsers were a nuisance, and maybe they should just be cut out entirely.
If Safari weren't such an important part of the market, Firefox would have been cut out long ago and we'd be awash in "Made For Chrome (and skinned Chrome)" badges. It is only the economic necessity of supporting iOS users that keeps cross browser development alive.
I don't usually resort to personalised dissection of post, but to be frank, you've taken a giant shit all over this subthread so I think it deserves it... this notion of yours seems to be the underlying theme of most all of your comments - that everyone here criticising webkit or Apple must be against browser diversity, be Google proponents, or not value stability, performance and privacy... We are not this caricature... It might be worth your while to take a second to reflect on that assumption and binary view of reality.
Thanks
It breaks in every major version that’s been released. Simply talk to any developer who has to do a significant amount of work building apps in Safari and they will tell you the same thing.
The webkit team is talented and do great work but this is simply a result of a decade of underfunding and it’s just not possible for them to maintain a modern browser with their current resources.
"misguided impression that it’s a good browser"..."Simply talk to any developer"
Your experience as a developer, and you dealing with utterly trivial regressions or handicaps, has shockingly little bearing on whether it is a "good browser" or not.
Don't build "apps" in the browser. Period. It's shitty, underperforming, and breaks all user expectations, regardless of the browser it's running on.
I've yet to see a single app, PWA or not, that wasn't so. Unless it's just a re-skin of a simple website with text and images, and a few forms, but then it's just a website, and if you can't make it run on Safari, go find a different job.
It's not necessary to talk about chromiums bleeding edge non-standard features, webkit easily has the least support for unopinionated standards released over the last decade and adopted by the other two.
> no platform uses the browser more than iOS users do. iOS users always are over-represented in web usage compared to marketshare.
What point are you trying to make here? iOS users have no choice but to use Safari. If you install firefox or chrome or anything that is a "browser" on an iOS device, it's forced to use Safari webengine underneath, so it's essentially safari with different UI, and this is apparent in the useragent string so any decent stats will show that essentially every iOS user == Safari user.
"What point are you trying to make here? iOS users have no choice but to use Safari."
Android users use the browser on their device -- any browser -- less than iOS users use their browser(s).
Read the Google corporate propaganda repeated on here, and other platforms provide a web bliss of PWAs, freed from app subservience. Only, not at all.
I have not seen such a great community on the internet before, so if you have any recommendations of forums like HN, it would be great!
Can't harass users with notifications.
Safari can open a pdf up like a native webpage in a tab. Until one of the Android browsers can do this out of the box (without having to use a ridiculous fork of Firefox so I can install extensions Mozilla doesn't want me to and installing pdf.js extension to use their own project), it will always be the superior browser.
If webkit was liberated from Apple I think it would ultimately benefit chromium as well.
I also support the stance that certain features should remain focused where they belong e.g. natively installed apps. But who can decide what should be a web standard and what shouldn't... it's hard to say. I think having a healthy governance and enforcement body is a prerequisite before we look at technical specifics.
https://developer.apple.com/safari/technology-preview/releas...
The vocal minority is a very tiny percentage of web developers who believe that whatever Chrome spits out is the bees knees, the modern standard, and all browsers must immediately have that.
Apple's investment in safari/webkit goes up and down. They've actually made a lot of investments since 2019 or so. Probably less so for the previous 6 years before that. But again, webkit was very innovative in the early 2010s