News for hackers. Stuff that matters.
Re:Google Chrome now works on iOS by ajross on Thursday June 28, 2012 @01:50PM (#4172898)
Can someone clarify? I thought replacing the browser (actually even stronger: rendering web content using anything but the browser) was one of the items forbidden by the app store guidelines?
Re:Google Chrome now works on iOS by speg on Thursday June 28, 2012 @01:53PM (#4172920)
While Chrome for iOS will include a number of key features, including incognito mode and tab syncing across devices, the browser will still use Apple's WebKit-based engine required by the App Store developer guidelines. It also will lack the Nitro JavaScript engine that Apple uses to speed Safari's performance.
Re:Google Chrome now works on iOS by kyrra on Thursday June 28, 2012 @02:00PM (#4172962)
Which is why I still like Android as a mobile platform. Google gives users a choice, Apple makes you live within their walled garden.
Re:Google Chrome now works on iOS by anextio on Thursday June 28, 2012 @02:29PM (#4173125)
V8 requires just-in-time compilation, which is not allowed on iOS for security-related reasons.
Re:Google Chrome now works on iOS by ricefield on Thursday June 28, 2012 @02:10PM (#4173017)
So, no V8 or Nitro, but Chrome/Chromium uses Webkit, so renders should be the same (just slower) right?
Re:Google Chrome now works on iOS by estel on Thursday June 28, 2012 @02:30PM (#4173130)
Well, Mobile Safari's webkit version will usually be somewhat behind the latest six-weekly Chrome release cycle.
Re:Google Chrome now works on iOS by bzbarsky on Thursday June 28, 2012 @04:56PM (#4173882)
The WebKit on iOS is rather different from all other WebKit ports in various ways (e.g. there are various -webkit CSS properties that are only supported by WebKit on iOS and not WebKit anywhere else). And of course there are lots of Chrome features.

So the renders may or may not be the same, depending. And various DOM features that are part of UIWebView won't be the same (e.g. any DOM or HTML feature that Chrome has but Mobile Safari does not will be missing).

Re:Google Chrome now works on iOS by wavephorm on Thursday June 28, 2012 @03:15PM (#4173390)

  still use Apple's WebKit-based engine required by the App Store developer guidelines
This is pretty retarded, and should really be looked at by the DoJ. To hobble all web browsers like this is something that even Microsoft, at the height of their dominance, didn't even attempt.
Re:Google Chrome now works on iOS by ajross on Thursday June 28, 2012 @03:47PM (#4173540)
Apple isn't dominant like Microsoft was, though (though I'll be honest that it looked for a year or two like they would be -- I'm still wiping the sweat from my brow over that). It's not enough to be anticompetetive under antitrust law, you have to be a monopoly too. Apple's hobbled third party browser environment isn't hindering android adoption, basically.
Re:Google Chrome now works on iOS by masklinn on Friday June 29, 2012 @08:54AM (#4176354)
> I thought replacing the browser (actually even stronger: rendering web content using anything but the browser) was one of the items forbidden by the app store guidelines?

The real case is somewhat more complex:

1. It is not possible to replace the built-in browser (there are no hooks to have an other application handle e.g. `http` links), but it is perfectly possible to release (and sell) a "browser" application through which websites can be accessed

2. It is allowed to render any content, but it is not allowed to execute downloaded code save through the built-in interpreter, so a browser can't run javascript code locally. On the other hand, it's perfectly possible to have a "thin-client" browser and do all rendering on a remote server, that's what Opera Mini does.

Re:Google Chrome now works on iOS by glhaynes on Thursday June 28, 2012 @01:52PM (#4172911)
It's still the system rendering and JavaScript engines.

Edit: Which, from the vast majority of users' perspectives, are functionally identical.