3 ms·
Everything on that list is relevant, but please keep in mind that banning custom browser engines isn't particularly bad thing for everyone. Of course Apple doi
by SXX 8y ago
Everything on that list is relevant, but please keep in mind that banning custom browser engines isn't particularly bad thing for everyone.
Of course Apple doing it to force web developers to keep supporting Safari since no one can simply expect iOS users to install Chrome, but it's also benefit open web greatly since it's preserve status quo that we have more than just one browser engine. The day Apple stop doing it would be the day web developers going to abandon support for Firefox too.
- ozten 8y agoI don't buy that a platform excluding rendering engines helps keep the web diverse and open. Apple has crippled the mobile web since iOS reinvented the category. How many years before the file upload widget worked?
- SXX 8y agoI myself had to fix weird Safari and sometimes even iOS-only bugs more than once, but it's just Apple cripple it's own platform. Also even if it's annoying for web developers these things still keep our eye keen on how what we work on look in something other than Chrome. Unfortunately Google has abysmal power over web right now and I cant count how many times I see them cripple experience for Firefox. Now they even outright saying that new Adwords interface only work in Chrome. And AMP only prove how little we can trust Google.
- deleted 8y ago[deleted]