One of the messages of the event is Google will maintain for now separate code bases for Android and Chrome OS--the minimalist operating system wrapped around its Chrome browser for notebook-like devices. On the show floor, Google had a large Chrome area (above) showcasing the browser and the Chromebook Pixel right next to an equally large Android area (below) where Nvidia and Qualcomm--among others--had supporting booths.
Google is creating technology but more significantly, they are accumulating data. People, places, things. The technology that they create enables them to accumulate more data. We go onto Google earth and say "ooh, cool, I should go visit Yosemite" and they way "ooh, cool, look at how many people are checking out Yosemite!" I'm curious what those google glasses are sending back for their data mining!
@DrQuine: Firefox and Chrome are both reliable here, under Windows and Linux. "Fast loading" is a different matter, but I generally load Firefox when I sit down and the machine, and just leave it running. If you are hopping in and out the way folks got accustomed to on Windows with IE, you're arguably doing it wrong.
"Bloat" is relative. Given the steady advance of web standards, and the need to support things like HTML5, CSS3, and the embedded video HTML5 is making [possible, well, code size *will* grow. Tell me what you would drop to shrink the size and still have a usable browser.
"Perfect is the enemy of good" - let us not forget that continuous efforts and enhancements to improve software sometimes result in a loss of the benefits that it originally provided. When Chrome (and competitor FireFox) were scrappy upstarts, they were fast and reliable. Now they're bloated and buggy. Can we get back to a reliable fast loading Chrome browser?
Join our online Radio Show on Friday 11th July starting at 2:00pm Eastern, when EETimes editor of all things fun and interesting, Max Maxfield, and embedded systems expert, Jack Ganssle, will debate as to just what is, and is not, and embedded system.