InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Details of the Now Available Google Chrome OS

Posted by Abel Avram on Nov 20, 2009

Sections
Development,
Operations & Infrastructure
Topics
.NET ,
Java ,
Operations ,
Ruby ,
Operating Systems ,
Architecture
Tags
Google

Google has open sourced Chrome OS a year before the planned launch which is to happen some time before winter holidays in 2010. Google is working with manufacturers on a new reference hardware to accommodate their speed and security requirements which are key features of their new operating system.

Since everyone knows how to use a browser, Google wants Chrome OS to look and feel like a browser. Practically, what the users gets is a Chrome browser on top of custom Linux based operating system which is completely hidden from the user for simplicity. The entire data is in the cloud, and it is not permanently saved locally. A copy of the data the user works on is kept locally as a cache for speed reasons. One implication is that editing a document means updating the copy in the cloud.

Google plans the actual market release 1 year from now. The currently proposed UI will change in time. The idea is to use pinned browser tabs which become application tabs and they don’t move as long as they are pinned so one can access email, calendar, docs or other chosen applications. They are the left 5 tabs in the picture below:

image

By clicking on the Chrome logo located on the top left corner, one can access the application menu shown below, a web page displaying all the applications the user can access, having the option to add more:

image

The UI of this page is subject to change. The applications are started as lightweight windows called panels and the can stay on top of the screen even if one chooses another tab in the browser or it can be minimized or closed.

Chrome OS is a completely open, non-proprietary OS. For example, by accessing an MS Excel file from a storage device (SD card), Chrome OS will access MS Windows Live to open it up, if that’s the online application configured to process such files:

image 

Chrome OS netbooks do not have HDDs but instead they use flash based memory solutions or solid state drives (SSD) for that. This improves the boot up speed a lot, currently being at 7 seconds but it is promised to be even faster. The firmware verifies the signature of the optimized kernel, and, if it is OK, it loads the kernel which in turn loads the browser. In case one signature is incorrect, possibly due to virus activity, the firmware will download a default safe kernel and OS, the whole process being automatic. This recovery is done without losing system or application data, without losing settings and even without losing the cache. Also, Chrome OS updates itself with newer versions when available.

Chrome OS security involves a complete separations of web applications running in tabs separated from each other and from the underlying system. The OS file system is read-only for protection. User data is stored on a different partition and it is encrypted using cryptographic random numbers. All the user data is synchronized with the cloud, the local storage being used just as a cache. So, in case the OS is infected or the computer is lost, the user can get another one and, by using his credentials, he will load the entire OS, applications and settings in a very short time.

Google is currently working with manufacturers to elaborate a new set of netbook hardware which comply with their speed and security needs. Also, Google requests the netbooks to be made a bit larger to accommodate a standard size keyboard and to have better mouse pads. Also, the reference hardware will include information about the screen resolution, probably specifying larger resolutions than are currently used in netbooks.

There are already several media and document editing applications supported. Playing videos, loading photos, editing documents are already working and anyone can access countless online applications. Chrome OS is not proprietary in any way.

The code is open source, downloadable, under the name Chromium OS and Google is going to use the same code trunk as everybody else, but their product will be most likely called Chrome OS. Google has also opened up the design documents disclosing their plans for the future and welcomes anyone wanting to participate.

Resources: Video Introducing Chrome OS, Source Code, UI Experiments, Design Documents.

Ugh. Doesn't look good. by Thomas Anderson Posted
  1. Back to top

    Ugh. Doesn't look good.

    by Thomas Anderson

    Ooooh, not sure if I like the idea of a gui that uses tabs as its core functionality. I prefer an actual window management option.

    If only Google used X like most Linux and just built a netbook friendly desktop environment on that.

Educational Content

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.