Is Google's slow Chrome for iOS a preview of Windows RT?
Google announced Chrome for iOS today. But it's not the same speedy browser everyone falls in love with on Windows and OS X. So why is Google bothering to release it? And will Chrome for Windows RT suffer the same fate?
Chrome for iOS isn't really Chrome, the browser that people fall in love with because it's so damn fast. Instead, it's a native iOS app that acts as a shell over the Mobile Safari engine.
And he explains the reason. In a word, security:
So why is Google bothering? Because Chrome is a delivery vehicle for Google services, and a way to get around pesky browser makers who might set privacy defaults that make it difficult for Google to tie all of your information together.
Those other browsers can throw a privacy-related monkey wrench into grand data-collection schemes. Earlier this year, for example, Google was caught deliberately circumventing privacy settings in Safari, by implementing a technical workaround that tricks the browser into accepting tracking cookies from a third-party site.
And Google's representative to the W3C has argued that it has "the option to reject" Do Not Track (DNT) requests coming from browsers that have the DNT setting on by default—specifically, Internet Explorer 10.
Using your own browser—even one that's relatively slow—is preferable.
Google's actually catching a break with Microsoft's decision to make an exception to its sandboxing rules for third-party browsers running on Windows 8. That option isn't available for Windows RT. I suspect we'll see a slow Chrome for Metro, built under the same restrictions as Chrome for iOS, when Windows RT ships this fall.