Google Chromium OS – first impression

I thought that I’d have a quick look at Google Chromium OS. I’m not sure that it’s living up to the hype yet.

Where did I get it?
So far it’s only available as a VMware or Sun Virtual box download. I downloaded both the VMWare .vmdk file and the Sun Virtual box .vdi files from http://gdgt.com/. I had problems with my VMWare installation so I thought I’d try it in Sun Virtual Box. I’m running Sun Virtual Box on a Windows 7 64-bit host.

First impressions
The Sun Virtual Box image doesn’t boot properly and only boots to a black screen. Because Sun Virtual Box can support VMWare images, I thought that I’d try the .vmdk file. I noticed other posts which recommend configuring the network in “bridged mode” and running Virtual Box with administrator credentials. I did both of these things and Chromium booted first time. I was presented with a simple login screen.
At this point I entered my gmail account details. The image uses a US keyboard so the @ symbol is “Shift-2”.

After login you see a very simple browser screen with your Google mail and Google calendar tabs. Other tabs can be opened and it can be used as s simple browser. At the moment, I can’t see much value in it, but couple it with some nicer fonts and the ability to save/sync your Google Docs to the local hard disk of a laptop/netbook or USB key and it could have potential.

What’s the point?

Perhaps one use could be for students to all be issued with their own OS and Docs on a USB key, all Docs are backed up centrally, but they could take their key to any machine and boot from it to get the same locked-down experience wherever they work.

Alternatively, banks could issue secure keys for online banking containing an OS that can only access the bank’s online banking site. This could greatly reduce online account fraud by only granting access to web based banking to people who have a physical device (encrypted USB key), know the password for the key as well as the online account password.

Google Chromium screenshot

Google’s “Let’s make the web faster” initiative

Google has launched a new initiative to encourage people to develop faster, more efficient web applications.

 

To do this, they have published tools for download (like Fiddler and HTTP Watch) on their website. They have also written articles which explain GZIP compression, prefetching, reducing HTML size and image sizes etc. These may all be of interest to performance testers as well as Google’s target audience (developers) so their site is well worth a read if you find yourself at a loose end.

 

http://code.google.com/speed – The main website

http://code.google.com/speed/articles/ – Articles describing different performance improving technologies / techniques

http://code.google.com/speed/downloads.html – Downloads of useful tools which can help developers to improve web performance.

Identify a web server

If ever you are asked to do a testing proof of concept and you need to quickly identify a web server type you can use idserve from Gibson Research Corporation. This sends a simple HTTP request to a webserver and presents the HTTP response headers to the user. This allows you to identify the server type which can be useful when working out the best way to write scripts to test the site.

The latest version also identifies non-HTTP server types (e.g. FTP, SMTP, POP or NEWS) and does reverse DNS lookups so that it can identify a server’s name if all you know is the IP address.

This can be downloaded from Steve Gibson’s website, along with a whole load of other utilities.

IdServe screenshotIf