<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Coming soon: Chrome for iPhone &amp; iPad</title>
	<atom:link href="http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 20:48:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Kevin C. Tofel</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841665</link>
		<dc:creator><![CDATA[Kevin C. Tofel]]></dc:creator>
		<pubDate>Wed, 16 May 2012 19:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841665</guid>
		<description><![CDATA[Given that Chrome is Webkit-based also, I think the bigger issue would be the JavaScript engine. Google couldn&#039;t use its V8 engine, nor would it be able to use Apple&#039;s Nitro, which is reserved for mobile Safari IIRC.]]></description>
		<content:encoded><![CDATA[<p>Given that Chrome is Webkit-based also, I think the bigger issue would be the JavaScript engine. Google couldn&#8217;t use its V8 engine, nor would it be able to use Apple&#8217;s Nitro, which is reserved for mobile Safari IIRC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Schwartz</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841659</link>
		<dc:creator><![CDATA[Greg Schwartz]]></dc:creator>
		<pubDate>Wed, 16 May 2012 18:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841659</guid>
		<description><![CDATA[What this article (and all the comments so far) fail to mention is that any third-party browser for iOS right now is just a &quot;reskinning&quot; of Safari.  Apple doesn&#039;t allow any third party HTML rendering engines on iOS, so everyone has to use Safari&#039;s Webkit rendering engine in their browser.  Chrome on iOS would have to do the same thing.  Sure, Google could add syncing and other features (as other third-party browsers do) to differentiate Chrome from others, but at it&#039;s heart, it still has to use the same engine as Safari.  Opera gets around this (sort of) by essentially &quot;streaming&quot; the web pages from their servers, but it&#039;s an exception...]]></description>
		<content:encoded><![CDATA[<p>What this article (and all the comments so far) fail to mention is that any third-party browser for iOS right now is just a &#8220;reskinning&#8221; of Safari.  Apple doesn&#8217;t allow any third party HTML rendering engines on iOS, so everyone has to use Safari&#8217;s Webkit rendering engine in their browser.  Chrome on iOS would have to do the same thing.  Sure, Google could add syncing and other features (as other third-party browsers do) to differentiate Chrome from others, but at it&#8217;s heart, it still has to use the same engine as Safari.  Opera gets around this (sort of) by essentially &#8220;streaming&#8221; the web pages from their servers, but it&#8217;s an exception&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shivesh Vishwanathan</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841530</link>
		<dc:creator><![CDATA[Shivesh Vishwanathan]]></dc:creator>
		<pubDate>Wed, 16 May 2012 06:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841530</guid>
		<description><![CDATA[One difference between the car or televisions and phones is that phone is also a platform. Restricting choices in browsers seems more like car companies taking exception to people installing any GPS device they want on their car. Not allowing a new engine is one thing - engine is an &#039;integral&#039; part of the car. Same goes for TV guide interface - it is integral to the TV.

I don&#039;t think browser is an integral part of a device. Apple might actually run into some difficulties if it defines what is &#039;integral&#039; too narrowly?]]></description>
		<content:encoded><![CDATA[<p>One difference between the car or televisions and phones is that phone is also a platform. Restricting choices in browsers seems more like car companies taking exception to people installing any GPS device they want on their car. Not allowing a new engine is one thing &#8211; engine is an &#8216;integral&#8217; part of the car. Same goes for TV guide interface &#8211; it is integral to the TV.</p>
<p>I don&#8217;t think browser is an integral part of a device. Apple might actually run into some difficulties if it defines what is &#8216;integral&#8217; too narrowly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deeceefar2</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841467</link>
		<dc:creator><![CDATA[deeceefar2]]></dc:creator>
		<pubDate>Wed, 16 May 2012 00:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841467</guid>
		<description><![CDATA[And the rest of my comment that got cut off during login...

So why move Chrome to iOS?  This is a preemptive move by Google.  Currently Apple has absolute control over their app ecosystem, but that hinges on one thing the lack of competing web app market places.  Currently Apple has been happy to play along with the browser improvements and is actively adding new features to their browsers, but they don&#039;t really have any particular interest in doing so.  They don&#039;t derive any revenue from the browser usage, and as things are beginning to shift back toward web apps and emerging standards compete against native app features they are going to reach a crossroads very soon.  Do they keep supporting innovative features in the browser that allow developers to parallel native features outside the app ecosystem?

Google has a significant interest in ensuring they maintain access to the cutting edge features of the emerging browser standards so they can leverage the browser as a gateway to their customers even on Apple&#039;s platform.  With the divide between Google and Apple growing, it makes since for Google to get their trojan horse into Apple&#039;s cash cow before Apple&#039;s priorities shift.  For example Google could release Google Maps as a web app as soon as Apple releases their new mapping system.

So this move seems inevitable to me, Google has to do it, and hopefully if Apple prevents them from innovating in this space.  Google can rely on regulatory pressure to ensure it happens because it is bad for consumers if Apple does not allow people to innovate in the browser space.

As to why chrome would be successful on iOS because it will be the fastest.  Google will spare no resources in making Chrome for iOS the fastest they possibly can and will consistently add new web standards because this will become a significant source of revenue for them.  Aside from that they can use Chrome as a platform across all computers and mobile devices to create a second tier of apps and services outside of the native platform environments.]]></description>
		<content:encoded><![CDATA[<p>And the rest of my comment that got cut off during login&#8230;</p>
<p>So why move Chrome to iOS?  This is a preemptive move by Google.  Currently Apple has absolute control over their app ecosystem, but that hinges on one thing the lack of competing web app market places.  Currently Apple has been happy to play along with the browser improvements and is actively adding new features to their browsers, but they don&#8217;t really have any particular interest in doing so.  They don&#8217;t derive any revenue from the browser usage, and as things are beginning to shift back toward web apps and emerging standards compete against native app features they are going to reach a crossroads very soon.  Do they keep supporting innovative features in the browser that allow developers to parallel native features outside the app ecosystem?</p>
<p>Google has a significant interest in ensuring they maintain access to the cutting edge features of the emerging browser standards so they can leverage the browser as a gateway to their customers even on Apple&#8217;s platform.  With the divide between Google and Apple growing, it makes since for Google to get their trojan horse into Apple&#8217;s cash cow before Apple&#8217;s priorities shift.  For example Google could release Google Maps as a web app as soon as Apple releases their new mapping system.</p>
<p>So this move seems inevitable to me, Google has to do it, and hopefully if Apple prevents them from innovating in this space.  Google can rely on regulatory pressure to ensure it happens because it is bad for consumers if Apple does not allow people to innovate in the browser space.</p>
<p>As to why chrome would be successful on iOS because it will be the fastest.  Google will spare no resources in making Chrome for iOS the fastest they possibly can and will consistently add new web standards because this will become a significant source of revenue for them.  Aside from that they can use Chrome as a platform across all computers and mobile devices to create a second tier of apps and services outside of the native platform environments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deeceefar2</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841465</link>
		<dc:creator><![CDATA[deeceefar2]]></dc:creator>
		<pubDate>Wed, 16 May 2012 00:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841465</guid>
		<description><![CDATA[It is absolutely anti-competitive, however I&#039;m not sure they satisfy any regulatory conditions to exert pressure on them.  Apple better hope that other tablets begin to compete or it will have regulatory issues on its hands.  Perhaps android was the best thing for their profit margins, allowing to exist in a two platform world and stave off regulatory issues for the short term.]]></description>
		<content:encoded><![CDATA[<p>It is absolutely anti-competitive, however I&#8217;m not sure they satisfy any regulatory conditions to exert pressure on them.  Apple better hope that other tablets begin to compete or it will have regulatory issues on its hands.  Perhaps android was the best thing for their profit margins, allowing to exist in a two platform world and stave off regulatory issues for the short term.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin Martinez</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841419</link>
		<dc:creator><![CDATA[Devin Martinez]]></dc:creator>
		<pubDate>Tue, 15 May 2012 21:21:50 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841419</guid>
		<description><![CDATA[I&#039;ve been using the GNex for a while now along with chrome, but I find safari to be a lot better, for that matter I find safari to run better then any browser I&#039;ve used on android. I don&#039;t see any reason for iOS to make any browser besides safari default]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using the GNex for a while now along with chrome, but I find safari to be a lot better, for that matter I find safari to run better then any browser I&#8217;ve used on android. I don&#8217;t see any reason for iOS to make any browser besides safari default</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lou Gagliardi</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841404</link>
		<dc:creator><![CDATA[Lou Gagliardi]]></dc:creator>
		<pubDate>Tue, 15 May 2012 18:55:01 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841404</guid>
		<description><![CDATA[If it does appear, I will be downloading it. I love Chrome]]></description>
		<content:encoded><![CDATA[<p>If it does appear, I will be downloading it. I love Chrome</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin C. Tofel</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841403</link>
		<dc:creator><![CDATA[Kevin C. Tofel]]></dc:creator>
		<pubDate>Tue, 15 May 2012 18:44:33 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841403</guid>
		<description><![CDATA[A S, I hear you, but it&#039;s their hardware and their software. IMO, this is no different than a television set with a proprietary guide interface. Should that TV maker be forced to use a different interface because it&#039;s the &quot;right thing to do&quot;? Believe me, I&#039;m all for choice! But I don&#039;t see how the courts can force Apple to allow the devices it builds to do something that Apple doesn&#039;t want them to do.]]></description>
		<content:encoded><![CDATA[<p>A S, I hear you, but it&#8217;s their hardware and their software. IMO, this is no different than a television set with a proprietary guide interface. Should that TV maker be forced to use a different interface because it&#8217;s the &#8220;right thing to do&#8221;? Believe me, I&#8217;m all for choice! But I don&#8217;t see how the courts can force Apple to allow the devices it builds to do something that Apple doesn&#8217;t want them to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A S</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841400</link>
		<dc:creator><![CDATA[A S]]></dc:creator>
		<pubDate>Tue, 15 May 2012 18:18:14 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841400</guid>
		<description><![CDATA[&gt; why would Apple allow for Safari not to be the default?

Due to public and/or regulatory pressure? As you mentioned, they did not allow third-party browsers in the past, but they allow that now. I doubt that they voluntarily decided to allow third-party browsers out of the goodness of their heart. Similarly, there&#039;s a good chance that they can be pressured to allow third-party browsers to be set as the default browser. After all, it&#039;s the right thing to do.]]></description>
		<content:encoded><![CDATA[<p>&gt; why would Apple allow for Safari not to be the default?</p>
<p>Due to public and/or regulatory pressure? As you mentioned, they did not allow third-party browsers in the past, but they allow that now. I doubt that they voluntarily decided to allow third-party browsers out of the goodness of their heart. Similarly, there&#8217;s a good chance that they can be pressured to allow third-party browsers to be set as the default browser. After all, it&#8217;s the right thing to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Tom Guarriello</title>
		<link>http://gigaom.com/2012/05/15/chrome-for-ios-coming-as-mobile-browser-wars-ensue/#comment-841388</link>
		<dc:creator><![CDATA[Dr. Tom Guarriello]]></dc:creator>
		<pubDate>Tue, 15 May 2012 17:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=521505#comment-841388</guid>
		<description><![CDATA[Is there a copy editor in the house?]]></description>
		<content:encoded><![CDATA[<p>Is there a copy editor in the house?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
