[its_so_on]

I'm telling you what happens if Apple allows Firefox to dominate the iOS ecosystem. It's easier to target, it's easier to get right as a single app on an android device, and it crushes Apple's ecosystem and differnetiation. They've fucked up letting chrome in and they need to remove it to set things right. It's that simple.

[mhurron]

That's a whole lot of stupid you're spitting out there, but honestly the part that is bugging me the worst is you keep confusing Chrome with Firefox.

[its_so_on]

Maybe I need to spell it out for you, but if Apple allows Chrome it has to allow Firefox. Any and every argument that would apply to one applies to the other.

[danilocampos]

You get that iOS Chrome is running the exact same WebKit as Mobile Safari, right? There's no fragmentation risk there.

[telcodud]

Why would you consider it fragmentation even if (and that's a big if...not going to happen) Apple allowed Chrome for iOS to use its own version of WebKit (and V8!) instead of UIWebView? That doesn't make any sense.

[danilocampos]

...Where once there was one rendering engine, now there would be two. That introduces fragmentation for any developers targeting web users on iOS devices, as there would surely be a handful of nuances differentiating the two. Even if those were just around performance.

I don't even think that matters very much, though – I'm just addressing the concern of the crazy fucker above.