Apple maps: how Google lost when everyone thought it had won

Re:Apple maps: how Google lost when everyone thought it had won by JohnTHaller on Monday November 11, 2013 @03:40PM (#6713864)

Chrome also can't cement itself on Chrome because of the anticompetitive browser rules Apple baked into iOS approval policies. That's why Chrome on iOS isn't actually Chrome. It's just a Chrome UI on top of Mobile Safari renderrer with the faster JS engine disabled so Safari itself maintains better performance against all comers.

[ Parent | on HN ]

Re:Apple maps: how Google lost when everyone thought it had won by gaius on Monday November 11, 2013 @04:37PM (#6714237)

Ah interesting. That's why it crashes on exactly the same pages that Safari does then.

[ Parent | on HN ]

Re:Apple maps: how Google lost when everyone thought it had won by JohnTHaller on Monday November 11, 2013 @05:09PM (#6714429)

Yup. Google can't use their shiny new optimized Webkit fork Blink they use on Windows, Mac, Linux and Android. They're stuck just using Safari without Nitro like all* other browsers on iOS.

* except Opera which was doing page rendering on a server farm in the cloud to get around the anti-competitive rules.

[ Parent | on HN ]