Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Chrome in iOS is quite a bit different from Chrome for desktops/computers anyway, so it likely wouldn't really play that much of a role if the desktop version is being forked or not.

Apple allows Mozilla on ios but they can't use safaris framework which makes any 3rd party browser slower. It's Mozilla who doesn't agree with it.
 
Chrome for iOS is pretty second rate compared to Safari. First of all, it is significantly slower. That's a fact due to it not being able to use the Javascript engine in Safari. In fact, because of this none of the 3rd party browsers will ever be as fast as Safari. You must work for Google or something.

Chrome is also lacking features. It's only just now getting full screen? This has been in Safari for half a year now. Ever since iOS6 was first introduced. And only now the ability to Print? That was like iOS 4 or something. Chrome also doesn't have the Reader feature, doesn't have Reading List, and doesn't work with iCloud like Safari and many other 3rd Party apps.

But really the main thing is just how much slower it is than Safari. Even if it could catch up in features that's a deal breaker for me.

Nitrous.

Chrome already had more screen estate visable, and has better tab syncing solutions than iCloud ever did, not least because they port to Windows.
 
I saw that and updated. I don't like the new font of the # of pages open.

----------

It can be very useful when printing postage labels. Buy postage online, print it thru Google Print if I'm not at home. Now I have the ability directly from my iPhone/iPad, even away. I find this very convenient. Airplay is restricted to being on the same wifi.

Google Print?
 
Please don't tell me you actually believe a theory made by some random developer.

The reason Apple does not allow access to Nitro is not to protect you, but to protect iOS from you. That is, they don't want to make it make it easy for you to jailbreak your iPad or iPhone.

Apple does not care about security as much as you think. Just look at the vulnerabilities they fixed in 6.1.3. I quote



4 out of 6 vulnerabilities deal with local users, as in the owner of the device, getting higher privileges or running code. That's not a security threat, unless you consider the owner of the device to be a malicious hacker.

Local user vulnerabilities such as these are important problems to fix even if Apple did not care about jailbreaking. They are also known as privilege escalation vulnerabilities. Any app you run, runs as a local user. Fixing these problems prevents you from 1) malicious apps and 2) buggy apps.

These types of vulnerabilities might also be used for rooting your phone, but if you can root your phone using an app, then it is likely that the same vulnerability could be used to access your private data such as your contacts, email, etc.

One of the first jailbreaks used a Safari vulnerability which allowed the user to just go to a URL in Safari and trigger the jailbreaking. This also meant your iPhone was vulnerable to hacks using the same technique as the jailbreak.
 
Please don't tell me you actually believe a theory made by some random developer.


4 out of 6 vulnerabilities deal with local users, as in the owner of the device, getting higher privileges or running code. That's not a security threat, unless you consider the owner of the device to be a malicious hacker.

I have no idea what developer you are talking about. I am using my knowledge of Nitro and iOS. Nitro uses a just in time compiler which can be dangerous if the app is rogue. And about the "LOCAL" vulnerabilities, you really have no idea what local means.
That means that any app, and webpage, anything the user does that is running as a local user is vulnerable. A rogue PDF (in the case of Jailbreakme.com) is a local vulnerability, so are apps.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.