This reflects a fundamental misunderstanding, much like how many think standards groups (e.g. W3C) decide how the browsers works.
(Standards groups can invent the best feature ever for the Web ... and it won't matter in the slightest if browser makers don't adopt it. ALL STANDARDS ARE SET BY BROWSER MAKERS ... the standards bodies are just the mechanism they use to do it.)
Likewise, the browser a web developer user uses is already set for them. EVERY web dev (except those at companies big enough to care about the "long tail" of browsers) uses one browser: the most popular one.
It has nothing to do with politics or being complicit, and everything to do with "You have a job to do, why would you make it take twice as long by testing everything with an unpopular browser, when 99 out of 100 times that testing will find nothing and be a total waste of your time?"
No, it doesn't. I wasn't talking about web standards bodies. I'm talking about the practical reality of the web as a platform that is resilient against slight differences between browsers. Such resilience can only come from developers who understand that their job is to target the web and not just Chrome.
It is you who misunderstands:
> It has nothing to do with politics or being complicit, and everything to do with "You have a job to do, why would you make it take twice as long by testing everything with an unpopular browser, when 99 out of 100 times that testing will find nothing and be a total waste of your time?"
You are literally arguing for the web to become the Chrome Platform for the convenience of web developers. Sure we can have other browsers, so long as they're perfectly compatible with Chrome's quirks. This is precisely what it means for the web to be the Chrome Platform, not the open web. We've already reached the point where it's assumed that Chrome is perfect and anything that deviates from Chrome is someone else's bug. It's sad.
The reality is that 99% of web developers all use the exact same browser, and it isn't Chrome or IE or any one browser its "whatever is the most popular browser currently" (really it's "most popular for your customers but 99% of companies have customers who use the same browsers as everyone else).
You can bury your head in the sand and say "oh the mean web developers aren't using my pet browser" ... but it won't change the fact that no one wants to test on an unpopular browser, then test again on a popular one: EVERYONE is going to test their site with the browser most likely to use that site.
You are correct that many developers complain about Safari because they are lazy little shits who would much prefer the whole world be forced to change which browser they use in order to make their jobs a bit easier.
Nobody is saying anyone needs to test on an unpopular browser. Safari on iOS is, by the numbers, very popular.
This is a wild statement. For an individual user, what is the point of browser diversity if you are locked into your browser by OS? A weird number of people here are okay with this particular example of anti-consumer behavior simply because it offsets the chrome monopoly. That's not a healthy web, that's competing layers of dysfunction.
Though an interesting consequence is that allowing iOS users to install firefox but not chrome would be a strict improvement over the current situation.
If diversity fails to occur naturally, some amount of forced diversity helps to keep the ecosystem healthy.
There's no reason for Safari to have a sub-par experience except for the laziness of some web developers.
How about a browser with a captive userbase that has less incentive to stay up to date with web standards?
Your argument is that we should expect developers to target/test their app on many different browsers where any random CSS property behaves differently. They will have to buy a device just for this purpose. Because it is obviously developers who should have to pick up the slack here, not Apple.
Safari is a better browser because it doesn’t support them.
> Safari is a better browser because it doesn’t support them.
It has supported them since iOS 16.4. The issue is they made enabling them so high friction for users that you're better off publishing a WebView wrapper to the App Store instead. More work for app devs, worse experience for users, but great for Apple because it's still on the App Store.
To me, chromium is the kernel and the browsers are the distro. We do like that there is a shared kernel in linux, yes?
I acknowledge that this is reductionist, as there exists another lack of diversity for consumer operating systems, in there really only being Windows and Mac / iOS and Android.
And the Linux kernel isn't a good analogy because the web is a standard, not an implementation. In that sense it's more akin to UNIX, or IP-based networking.
https://insights.linuxfoundation.org/project/chromium/contri...
Still, there is a difference between contribution and control, which I hope and dream can and will change.
https://www.learninternetgrow.com/who-controls-chromium/
I will add that I appreciate your response, generally, but especially the missing hyperbole. This civil discourse is very preferable.
Linux is GPLv2, it has many outside contributors, it was built from scratch, and it has Linus as a neutral party as the final decider in terms of the direction of the project and what gets included.
Chromium is a mix of LGPL, BSD, and other licenses depending on the component. Chromium was originally forked from WebKit; it isn’t a from scratch project. Google decides what changes get merged to Chromium.
However, if Apple allowed different browser engines, eventually no one would be able to choose anything but Chrome regardless of what phone they bought.
A bit of forced diversity is wildly preferable over another collapse towards monoculture.
Says who? I certainly don't agree with that statement, the "web as an open platform" was unrecognizable when proprietary clients were the norm.
(And before you say it, consumers can choose Android, where 99.9% of people use Chrome, but apparently that's okay because they "chose" it.)
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.
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.
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.
On macOS, Google plays with a lot of dark patterns to get people to install Chrome. I can't count the number of times I've visited my sister or parents and seen Chrome on their Mac, and their explanation is "because Google told me I needed it."
That's not choice either.
It sounds like your family is using Chrome because it's more convenient. It's 2026, we can't blame anyone given what Safari spent the past decade doing. Apple does not provide convenient Safari sync for Windows and Android devices, which comprise the majority of smart devices sold. They don't support the normie extensions that people use on Firefox and Chrome. Safari lags behind Chrome in features, WebKit lags behind Blink in cross-platform support, and Apple doesn't allow Safari forks to boost their market share. Apple draws very clear and arbitrary lines in the sand, and then redrafts them once they finally change their mind about PWAs or notification support. By the time it reaches Safari, your parents have been using the feature in Chrome for 8 months.
We may have to agree to disagree. Apple's incessant marketing for their own inferior, ad-ridden packin software is part of why I left macOS to begin with. It's infantilizing to be told that I can't be trusted to make a smart decision, when Apple's own suggestion is a half baked, self-serving alternative. I empathize with Mac users that ignore Safari because that's exactly what I did on my Mac, too. I'd have been using Chrome if Firefox wasn't an option. And I still would, because WebKit is a dog's dinner on my OS.
If you think my mother or sister have the faintest idea what a web browser is, or how one might be better than another, then you haven't met my mother or sister. To suggest that they made any kind of informed choice is absurd. They were influenced by marketing, plain and simple.
Personally, I'd be fascinated to see an in-depth study showing what percentage of web users chose their browser based on true/objective criteria, as opposed to marketing, brand preference, herd mentality, or wrong assumptions. Is exposing someone to marketing really what we mean by choice?
It's worth remembering that choice isn't necessarily the pure good we intuitively believe it to be. Western consumers have an extraordinary choice of food, yet that hasn't necessarily translated into healthier diets. This is especially problematic when the choices themselves are shaped by corporations whose interests aren't well aligned with the consumer's.
Apple is a corporation too, and they have their own (quite sizable) financial interest in gimping the web as an alternative to native app distribution. Apple used to recognize this, and prioritized interoperability with OpenGL and OpenCL as a hedge against the web becoming the only cross-platform API that the Mac supported. The Apple of today has abandoned those interests and lost all pretenses of humility. They are equally as mask-off as Google or Microsoft is, pushing Metal and WebKit just as shamelessly as Microsoft crams the corpse of DirectX into things. This isn't a charity project, it is another way for Apple to control iOS software distribution, their primary service cash cow, Tim Cook's pride and joy. Apple is happy to give Google money for their Apple Intelligence integration, this isn't a grudge that they take seriously.
Apple could have supported KHTML upstream, and killed Blink in the cradle. They could have made Safari a billion-dollar cross-platform product, and won. They made this horrible bed, and now they want to users to moralize Google's victory. Why would anyone, knowledgeable or naive, insult themselves by standing with Apple here?
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.
The only lie being told in all of this is the one Apple tells when you install Firefox on an iOS device. It's not Firefox you're installing, it's Safari. Every browser on iOS is Safari - you have no choice at all.
>The health of the web as an open platform is defined by browser diversity, not browser choice.
Then put your money where your mouth is. If Safari can compete then let other browser engines on iOS. If it can't then it deserves to die. Artificially inflating it by forcing on iOS isn't the utopia you think it is.
>A bit of forced diversity is wildly preferable over another collapse towards monoculture.
Apple iOS is a monocoulture - every browser is Safari whether you want it or not.
There's no argument you can make to escape the fact that Apple is helping nobody but Apple by forcing Safari on iOS.
This isn't browser diversity, iOS is a browser monoculture, it's all Safari under the hood. How can you not understand this??
Choice is what the individual (supposedly) has. Diversity is what actually exists across an ecosystem. iOS is the last bastion of browser diversity, because despite all this supposed "choice", it's pretty much all Chrome everywhere else.
https://github.com/minh-ton/reynard-browser
Real Gecko on iOS
Chromium on iOS can also be compiled with blink, using the ‘use_blink’ flag.
Maybe you don't understand that I have to spend several hundred dollars for the privilege to debug Safari's shitty bugs. That's FUCKED UP. It isn't "being lazy". I shouldn't have to spend money so I can cater to a shitty browser. And Apple does some weird-ass things with their browser that make it wonky, and you can't debug some things without an apple device. Touch events are one particular iffy thing Apple does differently, because "think different" apparently means "we do whatever the fuck we want so pay us to debug things that shouldn't need debugging".
>Testing your website on two browser engines (and accepting that not everything is going to work perfectly in both) is literally the lowest bar expected of you.
Give me $500 to buy an Apple device and I'll fix things so it works for the shitty browser iOS users are forced to use. It has not a single fucking thing to do with "being lazy", and you're a shitty person for suggesting that's how this works.
If the cost really is an issue for you, I'm sure you know that you aren't forced to pay $500 to Apple. You can easily find hand-me-down Apple devices that still runs a current operating system for a pittance -- or free if you have a network of friends or family. No need to pay Apple anything.
I wouldn't be complaining if I could install the iOS simulator on any other platform - but even on iOS the iOS simulator sucks badly, and it only works on MacOS. It doesn't "simulate" touch events as they function on a real iOS device.
Nobody says you need to pay Apple anything. Apple devices can be incredibly cheap on the second-hand market -- potentially free if you have friends or family. An older Mac and an iPhone 11 are all you really need. If that is still too much for you, then what can I say? I don't see Microsoft giving you a Windows PC or Google giving you an Android device for free.
I suppose you can quit your job and become a chef, but you'll still have to buy your own set of knives and an apron.
Tell me you're not a web developer without telling me you're not a web developer. And if you are, you must be new here, or really bad at it. I've been developing websites for 30+ years, so I have no doubt I've been in this game and paying attention way longer than you have. Go have a seat over there, this pointless internet interaction is OVER.
Only in your dim-witted head.
Go have a seat over there, this pointless internet interaction is OVER.
It's obvious Apple isn't doing this to "protect the open web" because if that was true, they wouldn't have stopped developing Safari for Windows.
Wild how low the bar has gotten. The web would be so much better if there were ~10 browsers, each with around 10% market share. Web sites would have to suck it up and put some effort into browser testing and compatibility. And stop relying on features of a single browser. I remember writing software that had to work on over a dozen platforms. But developers today can’t manage to support more than one browser?
If your website doesn't work on one browser, you probably need to raise a bug report for that browser rather than change your site.
There's multiple issues with Safari and people complaining aren't "lazy". To start with it's a much buggier browser than Firefox or Chrome. Sure if you go on caniuse.com, almost everything is marked as supported but with Safari in reality it's always ""supported"" and you will deal with non-sense bugs, most of the features are sort of 95% there and they stopped development claiming it's good enough. They also have very poor QA and regressions happen often.
Next, Safari is the last non-evergreen browser, it's still tied to the OS and thus lags behind in updates.
And to finish with, Safari is also only available on Apple devices (harder to test with) and tied to a specific OS version (how are you officially even supposed to test the bugs on version X without paying a third party company? I don't know).
I'm not against Safari but Apple really needs to put some money to make it more modern if they want to actually compete with Firefox or Chrome without their OS lock-in.
Lack of browser diversity is bad because it puts too much control in the hands of the only browser vendor.
Lack of browser choice is bad because it puts too much control in the hands of whatever browser vendor they use.
We need both for a healthy web.
[0] Imagine that everyone was mandated to use one of five different browser engines, such that each had exactly 20% market share.
[1] Imagine that you are free to choose between five different browser engines but everyone else picked #3 and websites are only ever tested on #3 and all the others don't work so well.
Remember, you are a web developer, not a chrome platform developer. Don’t be complicit in Google’s slow-moving coup.
The only people who complain about Safari are lazy web developers who fail to appreciate what it means for the web to be an open platform. Testing your website on two browser engines (and accepting that not everything is going to work perfectly in both) is literally the lowest bar expected of you.