Chromium OS - Digging deeper into the open source Chrome OS
By Dj Walker-Morgan
When Google announced Chrome OS, many people assumed Google was launching an assault on the desktop - going after Microsoft Windows and were just not saying that was what they were doing. Now Chromium OS, the open source branch of Chrome OS, has arrived The H has taken the source code and built it to see how it feels in practice.
Chromium OS is designed around one philosophy, that the web and web applications are all that a netbook needs. This was, notionally, the original idea behind netbooks such as the Eee PC 700 series, but that generation of netbooks rapidly developed into "tiny laptops" with similar, albeit scaled down, specifications to those of a laptop computer. They also included the same issues of laptops; data tended to be stored locally, there was little integration with the web and web applications and the browser was just another application. Netbooks like this have been successful in their own ways, but Google wanted something else to be in play in the market, a truly thin client environment where there was only one application running on the operating system, the browser.
What's inside Chromium OS?
Although Google's current release of Chromium OS can be run on current netbook devices, it is aimed at a device which doesn't, quite, exist yet; a tablet or clamshell device, possibly with touch support, definitely with 802.11n Wi-Fi and solid state storage. The storage on a Chrome OS device is there to act as a cache for data which is stored on the cloud, in Google's case, their clouds and services. This means that the cost of the device is lower as it does not need to include a large hard drive or flash drive.
The operating system itself is a lightweight Debian GNU/Linux based operating system which contrary to earlier rumours, includes, an X Window based windowing system with support for OpenGL and the Clutter UI animation library. The latter components play a part in providing the quite rich animation which appears on screen. An important change at the lower levels of Chrome OS, and one which cannot be tried out just yet, is Google's development of custom firmware for Chrome OS devices which is focussed on booting as quickly as possible by only looking for hardware expected by Chrome OS; this doesn't stop Chrome OS being booted on a device with a traditional BIOS, but it does mean that the boot time on these devices isn't as fast as Google is aiming for with custom firmware in place.