Back in early December last year Google announced a beta/developer program for their ChromeOS program. They were offering free notebook computers running ChromeOS to a limited number of people to test. Never to be one to pass up an opportunity for free toys, I signed up.
While I wasn't chosen in the original batch, it seems I wasn't totally forgotten about. Waiting for me on my desk when I came into work on Monday was a mysterious package without a return address label. Opening it up revealed it was from Google, and it contained a CR-48, a to test the Chrome OS operating system.
About 60,000 Cr-48s were manufactured to be distributed to testers and reviewers in early December 2010. On March 8, 2011, Google Product Management vice president Sundar Pichai stated that the last of the 60,000 Cr-48s had been shipped.
Acer and Samsung are both preparing to ship what are now referred to as "Chromebooks" on June 15th. The hardware specs are basically the same from the CR-48 prototype and the final development units, with a few tweaks. The CR-48 has a single-core Intel Atom, 1 USB and a VGA port, while the retail units have dual-core processors, multiple USB and mini-HDMI ports.
Since what I have is a reference hardware design, I'm not going to focus too specifically on that other than saying that I do like it. It has a very good feel to it, and using it as a reference I can guess that I'd like either the Samsung or Acer even better, with them being slightly thinner and lighter. But, I'm talking mostly about aesthetics, which is a matter of personal taste.
The real question is, is the hardware up the the job? The short answer for the CR-48 is "almost". I suspect the change to a dual-core processor on the retail units will change that to a "yes". The long answer is much more interesting, because it is challenges fundamental definitions of the current computing model. More on that in Part 2.
My tests consisted of doing what I normally do on the web. Web browsing, including some Javascript-heavy sites; watching video on YouTube, Hulu and Amazon; using interactive Flash-based interfaces such as Tenable's Security Center -- the Enterprise control center for Nessus; document editing and HTML/CSS/JS development.
My criteria were simple. Remember, I'm talking about hardware only here. Did the CR-48 have the tools needed for me to do my job? Did it perform without noticably straining, lag or delay? This is where we get the "almost" from.
First things first. I signed in and checked for updates. The version of ChromeOS on the unit was from December, and there have been several updates since then. The system took care of itself, updating in two steps quietly in the background to the latest release. On to the tests.
I had no problem smoothly streaming video from Hulu or YouTube at resolutions up to 720p. Watching both animation, such as an episode of the Simpsons or the trailer for Kung Fu Panda 2, and non-animated video like an episode of Seinfeld, both displayed fine.
BUT, going to the Kung Fu Panda 2 website, which is nothing but Flash and had the HD trailer embedded in the middle of the screen, cause the video to be choppy and sluggish. This is where I think the dual-core on the retail units will help. That being said, the Tenable Security Center interface is Flash-based and it responded without issue. Of course, it doesn't have everything moving and a video in the middle of it at the same time.
Google Mail, Maps, Calendar, Docs, Yahoo Mail, Zimbra and Turbo Tax Online are all javascript-heavy sites. I had no issues with any of them either rendering correctly or noticable delays in operation. Everything was snappy and crisp.
None of my other tasks did anything to stress the hardware. This machine isn't going to be playing the latest Call of Duty, but then again it isn't designed for it.
The bit I'm really interested in, from a work perspective, is the Citrix Connector which isn't available to the public, yet. This was highlighted at the recent Google I/O conference and is disabled in the current version of ChromeOS. I expect to see it made available on or before the date the official retail units ship.
In Part 2 I'll delve into the entire Cloud paradigm as Google is presenting it, and my experiences with it.