Commentary

Why Google's Chrome OS Doesn't Surprise Me One Bit

When Google first announced Android in late 2007, I began to wonder if Google would stop at smartphones. Then Google announced the Chrome browser in late 2008, which, from the very beginning, showed the underpinnings of a full operating system. Google's Chrome OS for netbooks, announced late yesterday, is the logical next step for Google to take.

When Google first announced Android in late 2007, I began to wonder if Google would stop at smartphones. Then Google announced the Chrome browser in late 2008, which, from the very beginning, showed the underpinnings of a full operating system. Google's Chrome OS for netbooks, announced late yesterday, is the logical next step for Google to take.Consider the amount of software and services that Google makes for PCs. Not just Web-based, mind you, but device-side software. Here's a short list: Chrome, Desktop, Earth, Picasa, and Pack. There's more.

Combine those utilities with Google's online software, and it's obvious that Google's services alone can handle nearly any task the Web users could have a need for. I use all of the Google services mentioned above, as well as its Web-based services such as Gmail, Apps, Docs, Sites, Calendar, Photos, Blogger, Reader and more. The few desktop apps I use for my daily duties are limited to Photoshop and iMovie.


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

When you add up all that Google has already built with the growing use of the Web for many computing and networking tasks, it's no surprise that Google would attempt to wrap everything together in one shiny package. Enter Chrome OS.

Google says very bluntly that Chrome OS is meant for those who spend most of their computing time on the Web. Sundar Pichai, VP Product Management and Linus Upson, Engineering Director, writes:

Speed, simplicity and security are the key aspects of Google Chrome OS. We're designing the OS to be fast and lightweight, to start up and get you onto the web in a few seconds. The user interface is minimal to stay out of your way, and most of the user experience takes place on the web. And as we did for the Google Chrome browser, we are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don't have to deal with viruses, malware and security updates. It should just work.
That all sounds good to me, but there are many other things to weigh here. How will Google solve issues such as integration with third-party devices? As it is, many suppliers of tech equipment already have two operating systems to support (three if you count Linux). Will they play ball and throw in support for Chrome OS, too.

And what about the viability of netbooks? They were all the rage the first quarter of 2009, but the Internet love affair with netbooks already appears to be fading. Does Google think it can keep the netbook category alive with Chrome OS, enhance it, dominate it?

Google says it is working with hardware vendors to bring the OS to market by mid-2010, but the OS will be open sourced later this year. I think it's pretty clear that "normal" PCs will still be required for the heavy lifting that is serious media manipulation and other intensive computing tasks.

Google also makes it clear that this is a different path from Android, its mobile operating system for smartphones. While there will be overlap between the two (duh), Google thinks that Chrome OS will be better suited to some tasks that Android just can't handle. How Google ties Chrome OS, its existing services, and Android together could spell the mobile computing paradigm of the future. Or, it could fall flat on its face.

Either way, this will definitely be an interesting product to watch evolve.

RELATED: Google Challenges Microsoft With New Chrome Operating System


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links