“The effect of this would be to force an independent browser like Firefox to build and maintain two separate browser implementations — a burden Apple themselves will not have to bear.”
…No? Apple won’t bear that burden because they’re going to keep using WebKit. Firefox can keep using WebKit. Not using WebKit is a choice, with pros and cons.
But then you read on and it says Apple is allowing the kit to not be used in the EU only. Outside of the EU, presumably, Firefox will still have to use the Webkit or whatever. So, while Apple uses its own engine in both the EU and the US on its phones, Firefox will be able to use its own engine in the EU, too, but will have to continue using Webkit in the US and other markets outside of the EU.
Well maybe Apple shouldn’t be so hostile to other browsers. Honestly I don’t see why Firefox would bother will web kit. If they might as well not make a iversion.
Wow, right up front, they’re being disingenuous:
…No? Apple won’t bear that burden because they’re going to keep using WebKit. Firefox can keep using WebKit. Not using WebKit is a choice, with pros and cons.
But then you read on and it says Apple is allowing the kit to not be used in the EU only. Outside of the EU, presumably, Firefox will still have to use the Webkit or whatever. So, while Apple uses its own engine in both the EU and the US on its phones, Firefox will be able to use its own engine in the EU, too, but will have to continue using Webkit in the US and other markets outside of the EU.
I’m not sure what disingenuous about that.
Well maybe Apple shouldn’t be so hostile to other browsers. Honestly I don’t see why Firefox would bother will web kit. If they might as well not make a iversion.