Chrome OS - first impressions (with screenshots)
21-11-2009 2009m 23:07 000000000000r door WielandLast Thursday, Google offered the world a first peek at its upcoming new operating system Chrome OS (Dutch, English). Perhaps more importantly, it released the code as open source. Even though Chrome OS is not expected to hit the market for another year, within hours someone had built an image that you can run on VMWare or VirtualBox. The image is widely available through p2p-networks, so I decided to give it a spin.
(Of course, since it's a precompiled image, it's impossible to tell whether it has been tampered with. Some malicious hacker may have slipped in a key logger or whatnot. Chrome OS requires you to log in using your Google credentials, so you may want to create a new account to make sure your real account stays safe. That's what I did, anyway.)
I fired up VirtualBox and created a new machine. I gave it 1GB of RAM and told VirtualBox we'd be running Debian, the distro Chrome OS is based on. I pointed VirtualBox to the image, and started the machine.
In Thursday's demo, Chrome OS took 7 seconds to boot. Running on my virtual machine, it needed just under 18 seconds. Here's the login screen:
In Chrome OS, there's no distinction between your local system and the Internet. Chrome OS is essentially Google's web browser Chrome running on a Linux kernel. The applications you're running are all web based and displayed in browser tabs, and your data is stored in the cloud. So I logged in using the Google account I just created.
That took me to a Chrome web browser tab that loaded my pristine Gmail inbox. More interesting however is the Chrome OS logo in the upper left corner of the screen. It's the tab that gives you access to other web applications Google has preinstalled on your system preselected for use in the Chrome OS cloud.
These applications are apparently put on a web page using Google's Short Links service, which is normally part of Google Apps. I suppose that's why I had to sign in again:
Which took me to the actual applications:
Most of the icons I clicked, opened a browser tab to load a familiar website like Gmail, Google Calendar or YouTube. Clicking 'Contacts' however opened a 'panel', a small overlay that loaded my Google contacts and let me chat with them using Google Talk, much the same way Google's IM service works from within Gmail:
I also tried the chess game that Google's Sundar Pichai demoed. It's a Flash game, and you can make it run full screen by pressing F11:
Chrome has Flash 10 installed. Running Chrome OS on a virtual machine is very likely the culprit, but I found that Flash applications consistently made the system become unresponsive. Both the chess game and my unsuccessful attempts at watching a video on YouTube ended in me rebooting the system. This also happened when I tried to use the Calculator application, which just opened an empty panel, no Flash involved.
Surfing the Internet, I stumbled upon one final interesting bit of information: Chrome's user agent string. Unlike the Chromium build I'm running on my regular Ubuntu desktop, it does not identify the OS as Linux, but as 'CrOS'.
The issues I encountered most likely were caused by the VM. But instability aside, running Chrome OS is, frankly, not very interesting (yet).
I'm sure that will change after another year(!) of development, when netbooks become available that are designed to be used with the OS.
But right now, Chrome OS is basically I geeky way to run the Chrome browser and use the web applications you're already familiar with.
The user agent string is cool, though.








Ma.gnolia
del.icio.us
digg
Technorati
NUjij.nl

22-11-2009 om 19:31 000000000000r
Wow, the guys at Google have invented Opera's Fast Dial... impressive...
Seriously, what am I missing? Google wants your OS to be portable and availanle everywhere, but by creating bookmarks to Google mail/docs/wave/etc and saving your sign-in-cookie we have this already on more (st)able systems.
23-11-2009 om 00:26 000000000000r
At this point, yes, you're right. Chrome OS is unfinished and it's not yet available on the hardware it's supposed to run on eventually (though I'm planning on compiling it to run on my Eee PC soon).
The point of Chrome OS, at least according to Google, is to cut out all the unnecessary bloat that traditional operating systems carry. If all you ever start your OS for is to fire up your browser, your browser might as well replace the OS. So Chrome OS does just that, without bootloaders, two rounds of hardware detection, etc. It's essentially the Chrome web browser running directly on a very slim Linux kernel.
Also, the way Google is implementing this, it's giving web apps direct access to hardware features that are normally unavailable to them - web games could use the GPU, for instance. That can help make web apps faster and more graphically appealing, and give them features that normally are only available to desktop applications.
Google has not introduced some amazing new service. It's trying to make existing products better.
Whether they'll succeed remains to be seen, but it's clear why Google is doing this. They're a web company, they make money online. If they can lure users away from the desktop and into the cloud, by offering them an equal or better experience, that means more revenue.
12-12-2009 om 00:18 000000000000r
[...] log.alamagordo.org » Blog Archive » Chrome OS – first impressions … [...]