131–140 of 240 posts
"This item cannot be installed in your device's country"
It's currently available in: United States, Canada, United Kingdom, France, Germany, Spain, Australia, Japan, Korea, Mexico, Argentina, Brazil Sundar, SVP of Chrome just said "We are working hard to bring this to more countries and should greatly expand within the next three months."
Sunspider results:
Stock - 3852.2ms
Chrome - 3131.8ms
edit:
I was curious and redid it after rebooting:
Stock - 2816.1ms
Chrome - 2928.1ms (!)
In case anyone is interested in full benchmarks:
Stock: http://u.42.pl/2HRq
Chrome: http://u.42.pl/2HRp
I wonder if/when the "Browser" app will get the hardware-accelerated canvas support. Currently, some of the canvas apps I've tried on ICS run worse than on Gingerbread. However, those same apps run acceptable in this Chrome beta.
My initial perception is that all the Chrome features are great, primarily the data syncing with my desktop browsers. But the rendering is flawed; it doesn't render like the standard Android browser, doesn't render like desktop Chrome, and doesn't seem to even render consistent to itself. For example, a few screenshots comparing the standard Browser view of this comment page and the way Chrome beta views it: Browser:…
I had been wondering whether Google would port Chrome to Android, or they would port Dalvik to Chrome. I'm still not ruling out the latter option.
Assuming that means "be able to run Dalvik bytecode in the browser", that doesn't help with all the Android APIs and such, so it's hard to see how it would be useful.
Earlier quoted context omitted.
This is common Google strategy. They are trying to build the future and pre-ICS devices are not the future. So they get shafted. Google may make unhappy customers this way, but they can move a lot faster than companies like Microsoft, who support everything back two decades or so sometimes.
Apple seems to be able to innovate iOS while providing robust and timely updates for older devices.
According to MG Siegler, Chrome is in the bizdev-required proprietary 'with Google' part of Android, not the Open Source part. http://parislemon.com/post/17215781807/chrome-for-android-th... That means we're stuck with legacy browsers in existing Androids and in the non-Google-blessed world (Amazon Fire and the billion Chinese phones and tablets).
I'm guessing this shares code with Chromium, so will it be open source too? EDIT: Looks potential: http://blog.chromium.org/2012/02/deeper-look-at-chrome-for-a... "With hardware-accelerated canvas, overflow scroll support, strong HTML5 video support, and new capabilities such as Indexed DB, WebWorkers and Web Sockets, Chrome for Android is a solid platform for developing web content on mobile devices."
"Much of the code for Chrome for Android is already shared with Chromium and over the coming weeks, the Chromium team will be upstreaming many new components developed for Chrome for Android to Chromium, WebKit and other projects."
Chrome for iOS please.
Apple doesn't allow applications to provide their own runtimes: “3.3.2 An Application may not download or install executable code. Interpreted code may only be used in an Application if all scripts, code and interpreters are packaged in the Application and not downloaded. The only exception to the foregoing is scripts and code downloaded and run by Apple’s built-in WebKit framework.”