Google Archive

InfoWorld's Galen Gruman writes that the main potential game-changing attribute of the Nexus One - that Google is selling the device direct - does nothing to move the industry past carrier lock-in. "At first, I wanted to credit Google for making a tentative step in the direction of smartphone freedom. But that step is so tentative and ineffectual that frankly I think it's a cynical fig leaf covering the usual practices," Gruman writes. At issue is a political battle regarding walled gardens in the U.S. cellular market, a fight that will take years to result in any true consumer freedom. "The only way we'll ever get the ability to choose a smartphone and carrier independently is for the platform providers that count - Apple, Google, and RIM - to first develop only multiband 'world' smartphones and then refuse to sell their devices (or in Google's case, use its Android license to forbid the sale of devices) to carriers that block or interfere with device portability."

Like I said in the below item, it's a slow news day. This was further evidenced today by a story about the Google Chrome OS Netbook specifications, which, according to IBTimes, were leaked - to them, obviously. Together with the iPhone/NYC thing, this story gripped the internet and blogosphere today.

The past few weeks the entire internet has been going bonkers over the Google phone, yet another in a long line of Android phones that has everyone's knickers in twists. Up until now we had to go by small photos and Twitter messages from Google employees, but now we have full specifications, a hands-on, and video.

InfoWorld's Mel Beckman conjectures on the functionality necessary to make the Google 'smartbook dream' a reality, prioritizing the features any smartphone/netbook hybrid would require to succeed. From multitouch, to SSDs, to dual-boot capabilities, the list goes beyond what early Android-based entrants have to offer but remains within the realm of possibility, especially if Google CEO Eric Schmidt's hints at a future Chrome/Android OS convergence come to fruition.

As most of you will know, a common problem for any new operating system is hardware support. Drivers don't grow on trees, and usually need to be written by manufacturers, which costs time and money. Luckily for Chrome OS, it uses the Linux kernel which makes the hardware support question far less problematic. Still, when it comes to printers, the situation is different, and here, Google is trying to achieve something which should've been done ages ago.

Google has put up a very interesting document explaining the security features underlying its Chrome OS. The document also details the underlying guiding principles of Chrome OS' security features.