Lately, web developers have begun to question Apple’s monopoly over browser rendering engines on iOS. The App Store rules force browsers on iOS to use the same rendering engine as Safari instead of using their own, as they do on every other platform, including macOS. I’ve written about this before and why this is a problem.
Even some market regulators have picked up on this sentiment. And last year, the British CMA published a preliminary report which may result in rules being imposed on Apple to force them to allow other rendering engines.
But I’ve also seen some responses that argue that having less choice is good for users. Apparently, iOS is the last bastion of WebKit that can prevent a Chromium monoculture. And if we allow Chromium on iOS, WebKit will be doomed, and we will end up with Chromium everywhere.
Continue reading “Why Safari does not need any protection from Chromium”