ChromeOS: Not Yet For Civilians
For now, ChromeOS is pretty boring: after a bit of work, you get a fast loading browser, the ability to change a few themes, and if you’re a developer, access to a new platform. Google’s new ChromeOS is an operating system, but it’s strongly browser-based, and therefore is different than Mac’s MacOS and Windows– even from Linux. It’s designed to be extremely lightweight. Some call it a web appliance, and that’s partially true. It uses no hard disk, but that’s a red herring, as it uses and needs storage– but not much unless the usage profile of ChromeOS changes. For now, most people can ignore it. There’s nothing revolutionary about it.
There’s also a lot of confusion from Google, as Chrome-the-browser and Chrome-the-OS are used almost interchangeably. We even found this to be true when downloading and compiling ChromeOS for use. The two are separate entities, one the browser application, and the other is the appliance/OS substrate needed to anneal Chrome-the-browser to hardware and give it tools and native apps.
Initially, Google recommends running the ChromeOS guts as a job under Ubuntu Linux. Eventually, ChromeOS fits into a category called a semi-persistent instance. It uses no traditional hard drive for storage, and essentially launches as a completely self-contained browser-only instance. We downloaded Ubuntu 9.10 and installed it as a virtual machine. Indeed ChromeOS eventually becomes an appliance. Handily, Java and Flash are supported. Only the oracles know if Microsoft’s Silverlite components will run.
One of the closest conceptual operating system schemes to ChromeOS is Sun’s Containers system that works with Oracle/Sun’s Solaris, or perhaps Parallel’s Virtuozzo. Both of these ‘sandbox’ applications into their own metaphorically walled areas. Core operating system resources are available, but the applications are highly isolated from the operating system and its components– as well as other running applications.
ChromeOS seems poised towards very small systems (think netbook or notebook or OEM refrigerator display-type) web application running machine. It lends itself towards use of Google’s own web applications, but could conceivably be poised as an Android (Google’s mobile/cell phone OS) for larger platforms. Common interoperability between ChromeOS and Android are unknown at this moment, and probably is doubtful. Both of these operating systems are community/open operating system development platforms. None of them will pay developers the first dime for at least a year– which is Google’s ostensible target release date for ChromeOS.
The much pre-announced ChromeOS is now available for download as a kit rather than something consumers can munch on. If you’re a civilian, don’t even try, as the OS has to be compiled, and even for an operating system, it’s not a pretty picture. It’s do-able if you’ve ever compiled Linux or BSD from a CVS (not the drug store).
What ChromeOS Does
ChromeOS is a cloud operating system in the sense that most applications and storage will be used on hosted computers somewhere else, the kind that comprise corporate data centers and hosted/cloud environments. The light weight part of it has been done as well. FastScale, now owned by EMC, has a black belt in stripping the unused pieces from current operating systems into lightweight server operating systems in virtual environments. Nlight does the same thing for Windows clients, and is used frequently for virtual desktop interface environments that use ‘terminal server’ like virtual machines for remote users.
What Google might be trying to attempt is to bring one of Scott McNealy and Larry Ellison’s ideas to fore: the network as the computer. Of course the fact that Google’s Eric Schmidt once worked at Sun and Microsoft rival Novell (now owner of popular Linux distro Novell/SUSE) probably has nothing to do with this invention in Chrome. After all, be it ever so crumble, there’s no plate like Chrome……