<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Deep Jive Interests &#187; Hardware Strategy</title>
	<atom:link href="http://www.deepjiveinterests.com/tag/hardware-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.deepjiveinterests.com</link>
	<description>Thoughts on Web 2.0, Social Media, Marketing.</description>
	<lastBuildDate>Thu, 23 Dec 2010 02:51:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Google OS&#8217;s Hardware Strategy?</title>
		<link>http://www.deepjiveinterests.com/2009/07/10/google-oss-hardware-strategy/</link>
		<comments>http://www.deepjiveinterests.com/2009/07/10/google-oss-hardware-strategy/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 14:14:05 +0000</pubDate>
		<dc:creator>Tony Hung</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Google OS]]></category>
		<category><![CDATA[Hardware Strategy]]></category>
		<category><![CDATA[Intel]]></category>

		<guid isPermaLink="false">http://www.deepjiveinterests.com/?p=1545</guid>
		<description><![CDATA[Perhaps the key to Google OS&#8217;s success is in this key statement that might have been overlooked yesterday: Messrs. Schmidt and Page were also careful not to position Chrome as a competitor to Microsoft Windows. They argued that Chrome will (&#8230;)</p><p><a href="http://www.deepjiveinterests.com/2009/07/10/google-oss-hardware-strategy/">Read the rest of this entry &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<p>Perhaps the key to Google OS&#8217;s success is in this key statement that might have been <a href="http://blogs.wsj.com/digits/2009/07/09/sun-valley-schmidt-didnt-want-to-build-chrome-initially-he-says/" onclick="javascript:pageTracker._trackPageview('/outbound/article/blogs.wsj.com');" target="_blank">overlooked yesterday</a>:</p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">Messrs. Schmidt and Page were also careful not to position Chrome as a competitor to Microsoft Windows. They argued that Chrome will expand the market for netbooks, rather than eating into Windows’ share of the netbook market.</div>
<blockquote><p>Messrs. Schmidt and Page were also careful not to position Chrome as a competitor to Microsoft Windows. They argued that Chrome will expand the market for netbooks, rather than eating into Windows’ share of the netbook market.</p></blockquote>
<div>Rather than the hubaloo around &#8220;of course Chrome is a competitor&#8221;, I find the more interesting statment the latter half of that statement &#8212; Google&#8217;s planning to expand the market for netbooks.  I&#8217;ve no idea exactly how they&#8217;re going to get as-yet non-existent web-based operating system to drive the market for what is essentially a thin-client technology, but it does make you wonder about the <a href="http://www.pcworld.com/article/168196/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.pcworld.com');" target="_blank">growing relationship between Intel and Google</a> &#8230; and it also makes you wonder exactly how important the hardware relationships it has with its other potential vendors, and how, precisely, this particular free OS pre-installed will be different (and *grow* a market segment)  than the *other* free OS pre-installed.</div>
<blockquote>
<div></div>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.deepjiveinterests.com/2009/07/10/google-oss-hardware-strategy/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

