HTML5 on Android Samsung Galaxy Tab "disappointing" vs Apple iPad
appleinsider.com
appleinsider.com
I've often wondered whether Android's default browser (MicroB) being bundled with the OS will prove to be a blessing or a curse. It's nice that it's always there and loads quickly due to WebKit being a part of the OS, but as part of the OS it's subject to the OS's release cycle, which is in the hands of the carriers and we all know how that tends to play out on Android. With a browser from the Android Market, users get updates much faster, and that's a tremendous advantage over MicroB, which, depending on the device and carrier, may not get updates at all.
I hope we could do the best of both worlds and make the browser a separate app that got updates from the market, like Maps, Gmail, etc, but still run webkit.
I'm interested if this is because the browser app runs with default support for all screens. I wonder if you built an app that supported large/high-density screens and used a webview if you'd get the same scaling or if it would give you 1:1. I'll have to look into that.
Though what's the deal with the caption on the SunSpider benchmark (the one where they don't note that smaller=better): They say that "iOS takes advantage of the GPU as well, so scores here do not reflect actual performance".
What? The GPU has zero relevance to base JavaScript performance, and that aside is idiocy.
The website on which the news was posted may have an Apple bias, but the reviewer doesn't.
Software and hardware acceleration frameworks matter far more in mobile than on the desktop, where battery life, memory, and CPU tuning are crucial and painfully clear when you care about speed.
However yes the GPU absolutely matters in some cases. They should print those benchmarks if their goal is making lemonade, however. They shouldn't just try to manufacture reality.
It's poor writing, but it's not such poor writing that something that begins "SunSpider JavaScript benchmarks only test the CPU..." can be interpreted to mean exactly the opposite without a pretty aggressive presumption of bias on the part of the reader.
They definitely shouldn't include it and then include a completely unsupported (and technically irrelevant) trump statement. That single caption says all that needs to be said about that article.