3 ms·

I’ll start supporting support for third party web engines on iOS when Google and Mozilla start putting efficiency first and whizz-bang features second. I have z

I’ll start supporting support for third party web engines on iOS when Google and Mozilla start putting efficiency first and whizz-bang features second. I have zero desire to be forced into using Chrome on my iPad and iPhone and taking a hit to battery life because front end web devs couldn’t be bothered to support Safari properly, which will most assuredly happen shortly after thirty party engine support had been added.

arvinsim 8y ago
How does allowing Chrome on iPad/iPhone equate to being forced to use them?
- kitsunesoba 8y ago
  Because if they’re available, it’s then possible for web developers to use the old “go download Chrome to use this site” cop out and then stop supporting mobile Safari. After a while, so many sites will fail to work properly in Safari that the only choice I’ll have if I want a smooth browsing experience is to give in and use Chrome. It’ll be like the 90’s with IE except this time the monopoly browser is “good” so the monopoly is somehow OK. You see this happening with sites and web apps not intended for mobile use already. Once WebKit is no longer the only option on iOS, Chrome will take over entirely.