Commentary

Serdar Yegulalp
 

Android And Chrome OS: Google Vs. Google?

Would Google's Chrome OS spell more competition for Android than anything else? That's one of the possibilities looming for Google's browser-centric Linux distro, as on each closer inspection it looks that much less like a Windows killer.

Would Google's Chrome OS spell more competition for Android than anything else? That's one of the possibilities looming for Google's browser-centric Linux distro, as on each closer inspection it looks that much less like a Windows killer.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Not that many people, Google included, ever believed that was the idea. By Google's own admission, both Android and Chrome OS are "flanking technologies" -- designed to be companions to the desktop and not replacements. Both are open source, but according to one rather jaundiced view of Android as an open source project, that means not a blossoming of possibilities but instead a splintering:

The open source community is much more likely, based on its history, to screw around with umpteen hundred variations that are piled willy-nilly on top of umpteen OS variants, creating a mess that only a few nerds will want to play with.

Does this mean Chrome OS is doomed to follow the same steps? It might not, actually. Google did a smart thing by aiming to have third-party Chrome (and Chrome OS) development be no more difficult than writing extensions for the web itself -- making it a lot easier to create for Chrome (OS) than for Android, and thus stealing some developer attention away from the latter for the sake of the former. At least until Google's long-distance musings about merging the two come to fruition, which could be years off.

The end user, on the other hand, ought to be benefit. Most people are not going to be forced to choose between an Android phone and a Chrome OS netbook -- they could very well have both, since they're provided through different markets and satisfy different needs. But there's far more of a market case for Android right now than Chrome OS; the latter could turn out to be, like the grossly overpriced and underpowered litl, a solution with no real problem. The only problem that might end up being solved is how to get dependable hardware support for end-user Linux. Answer: create branded devices that follow a strictly-defined spec -- something Apple's been doing for ages.

Even if the goal is not to replace the desktop, the desktop itself is becoming that much more portable in every form, more so with every passing quarter. By the time Chrome OS is released to a public already used to Windows 7 (and maybe also an Apple tablet device), what flanking will be possible?

Our "A New IT Manifesto" report looks at a variety of new approaches and technologies that let IT rebels take on a whole new role, enhancing their companies' competitiveness and engaging their entire organizations more intimately with customers. Download the report here (registration required).

Twitter: Me | InformationWeek
Facebook: InformationWeek


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