<?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/"
		>
<channel>
	<title>Comments on: The Importance Of Chrome</title>
	<atom:link href="http://infrequently.org/2008/09/the-importance-of-chrome/feed/" rel="self" type="application/rss+xml" />
	<link>http://infrequently.org/2008/09/the-importance-of-chrome/</link>
	<description></description>
	<lastBuildDate>Thu, 10 May 2012 17:22:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Frank</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235233</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Thu, 18 Sep 2008 17:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235233</guid>
		<description>Stephan, 
That idea was originally what IE wanted with ActiveX.  Now, look at all the problems it&#039;s causing Microsoft and Vista.  The real problem of plugins is that they are often used for trivial features, ways that don&#039;t really deserve to be part of a plugin.  I mean, who cares if your cursor can be changed at a whim, or that the background of a page can vary based on your MP3 list?</description>
		<content:encoded><![CDATA[<p>Stephan,<br />
That idea was originally what IE wanted with ActiveX.  Now, look at all the problems it&#8217;s causing Microsoft and Vista.  The real problem of plugins is that they are often used for trivial features, ways that don&#8217;t really deserve to be part of a plugin.  I mean, who cares if your cursor can be changed at a whim, or that the background of a page can vary based on your MP3 list?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrome just Changed the Game &#8212; Oddly Zen</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235158</link>
		<dc:creator>Chrome just Changed the Game &#8212; Oddly Zen</dc:creator>
		<pubDate>Sun, 07 Sep 2008 22:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235158</guid>
		<description>[...] as first-class citizens.  Our web apps will access our systems like desktop applications. We get Gears baked in (note the lack of “Google” prefix — it’s now simply “of the web”) and if you’ve read [...]</description>
		<content:encoded><![CDATA[<p>[...] as first-class citizens.  Our web apps will access our systems like desktop applications. We get Gears baked in (note the lack of “Google” prefix — it’s now simply “of the web”) and if you’ve read [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Martindale</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235134</link>
		<dc:creator>Stephen Martindale</dc:creator>
		<pubDate>Thu, 04 Sep 2008 19:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235134</guid>
		<description>All Google need to do is make their plug-in experience more convenient than every other browser&#039;s.

Sadly, the &quot;bad guys&quot; killed the plugin scene when they used early plugin mechanisms to install crap-ware on people&#039;s browsers. Today, plugins are a chore because you first have to wade through tons of security warnings and little yellow bars before you even get to the bit where the plugin starts downloading.

If Google used their continent sized brain and interstellar infrastructure to create a mechanism with which signed plugins could be installed in full user-confidence with no more than one click, they&#039;d be winning.

If they could do that without the required browser restart, they&#039;d be untouchable.

Instead of this...

1. Visit Site.
2. Notice expected content is not shown.
3. Notice annoying yellow bar saying the site either needs a plugin or couldn&#039;t install a required plugin.
4. Click multiple times to dismiss the yellow bar and all the associated security warnings.
5. Wait for plugin to download.
6. Finish what you&#039;re doing on every other tab.
7. Restart browser.
8. Use page with plugin.

You would have...

1. Visit page.
2. Notice that instead of the requested page you see a nicely designed page (like the default Chrome start page, which I love to bits) displaying some information about a required plugin, the fact that it is signed by a trusted CA and a single button to download and install it.
3. Click once and watch the plugin install.
4. Notice that the page you requested loaded automatically immediately after the install finished.

Wow: 4 steps instead of 8, with no &quot;secret-handshakes&quot; or popups. It&#039;s U.I. utopia.</description>
		<content:encoded><![CDATA[<p>All Google need to do is make their plug-in experience more convenient than every other browser&#8217;s.</p>
<p>Sadly, the &#8220;bad guys&#8221; killed the plugin scene when they used early plugin mechanisms to install crap-ware on people&#8217;s browsers. Today, plugins are a chore because you first have to wade through tons of security warnings and little yellow bars before you even get to the bit where the plugin starts downloading.</p>
<p>If Google used their continent sized brain and interstellar infrastructure to create a mechanism with which signed plugins could be installed in full user-confidence with no more than one click, they&#8217;d be winning.</p>
<p>If they could do that without the required browser restart, they&#8217;d be untouchable.</p>
<p>Instead of this&#8230;</p>
<p>1. Visit Site.<br />
2. Notice expected content is not shown.<br />
3. Notice annoying yellow bar saying the site either needs a plugin or couldn&#8217;t install a required plugin.<br />
4. Click multiple times to dismiss the yellow bar and all the associated security warnings.<br />
5. Wait for plugin to download.<br />
6. Finish what you&#8217;re doing on every other tab.<br />
7. Restart browser.<br />
8. Use page with plugin.</p>
<p>You would have&#8230;</p>
<p>1. Visit page.<br />
2. Notice that instead of the requested page you see a nicely designed page (like the default Chrome start page, which I love to bits) displaying some information about a required plugin, the fact that it is signed by a trusted CA and a single button to download and install it.<br />
3. Click once and watch the plugin install.<br />
4. Notice that the page you requested loaded automatically immediately after the install finished.</p>
<p>Wow: 4 steps instead of 8, with no &#8220;secret-handshakes&#8221; or popups. It&#8217;s U.I. utopia.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Wilcox</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235119</link>
		<dc:creator>Matt Wilcox</dc:creator>
		<pubDate>Wed, 03 Sep 2008 12:29:45 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235119</guid>
		<description>Alex, I mean the extensions. For me, what makes Firefox an indispensable tool isn&#039;t it&#039;s stability, or it&#039;s speed, but it&#039;s extensions: Web Dev Toolbar and Firebug for example. I either missed that completely when scanning over the comic, or there&#039;s been no mention of it.

I like Chrome, I like the out-of-the-way UI and the blistering speed, but I&#039;ll not use it until I can install functionality I want on-demand.</description>
		<content:encoded><![CDATA[<p>Alex, I mean the extensions. For me, what makes Firefox an indispensable tool isn&#8217;t it&#8217;s stability, or it&#8217;s speed, but it&#8217;s extensions: Web Dev Toolbar and Firebug for example. I either missed that completely when scanning over the comic, or there&#8217;s been no mention of it.</p>
<p>I like Chrome, I like the out-of-the-way UI and the blistering speed, but I&#8217;ll not use it until I can install functionality I want on-demand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235110</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Wed, 03 Sep 2008 00:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235110</guid>
		<description>Manuel:

The stats for auto-updating browsers and plugins give me some real hope that auto-updates do, over the broader population, work. Obviously enterprises want and need control over the process, but in the main, auto-update is a Good Thing (TM) and it works (assuming the update mechanism is non-evil and continues to have user trust).

Regards</description>
		<content:encoded><![CDATA[<p>Manuel:</p>
<p>The stats for auto-updating browsers and plugins give me some real hope that auto-updates do, over the broader population, work. Obviously enterprises want and need control over the process, but in the main, auto-update is a Good Thing (TM) and it works (assuming the update mechanism is non-evil and continues to have user trust).</p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuel</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235109</link>
		<dc:creator>Manuel</dc:creator>
		<pubDate>Tue, 02 Sep 2008 23:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235109</guid>
		<description>&lt;blockquote&gt;
It revs independently of browsers, implements new features without users changing their day-to-day choices, and has a (frequently exercised) auto-update mechanism. In short, it’s even more cross-platform than a browser. A plugin absolutely can (and will) help the web evolve. It’ll be gears or it’ll be Flash/Silverlight, which, written another way is “open vs. closed”.
&lt;/blockquote&gt;

I know very little about Gears admittedly. However nothing you have said he turns me on. I, and many of us, don&#039;t turn on auto-updates cause more often than not, they screw things up. I would have a problem with any plugin/standalone product implementing new features without me being able to veto that update.</description>
		<content:encoded><![CDATA[<blockquote><p>
It revs independently of browsers, implements new features without users changing their day-to-day choices, and has a (frequently exercised) auto-update mechanism. In short, it’s even more cross-platform than a browser. A plugin absolutely can (and will) help the web evolve. It’ll be gears or it’ll be Flash/Silverlight, which, written another way is “open vs. closed”.
</p></blockquote>
<p>I know very little about Gears admittedly. However nothing you have said he turns me on. I, and many of us, don&#8217;t turn on auto-updates cause more often than not, they screw things up. I would have a problem with any plugin/standalone product implementing new features without me being able to veto that update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235102</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Tue, 02 Sep 2008 20:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235102</guid>
		<description>Brad:

Obviously, since you&#039;re at Google you can&#039;t just come out and say this, but I certainly does seem weird that the folks at Mozilla don&#039;t just ship Gears (and pull the same &quot;hot patch IE if installed&quot; trick I suggested that Chrome use). They are 100% aligned on the merits, and if Mozilla still wanted full control over the content author experience, they could simply try to create a separate distribution channel or forge a distribution deal for Gears as they have for the browser in general (say, for every Gears install via FF that also patches IE, some extra dough for MoFo).

It&#039;s insane that MoFo isn&#039;t chasing down all the angles here.

Regards

&lt;b&gt;Update:&lt;/b&gt; changed the language to more accurately reflect what I meant to say.</description>
		<content:encoded><![CDATA[<p>Brad:</p>
<p>Obviously, since you&#8217;re at Google you can&#8217;t just come out and say this, but I certainly does seem weird that the folks at Mozilla don&#8217;t just ship Gears (and pull the same &#8220;hot patch IE if installed&#8221; trick I suggested that Chrome use). They are 100% aligned on the merits, and if Mozilla still wanted full control over the content author experience, they could simply try to create a separate distribution channel or forge a distribution deal for Gears as they have for the browser in general (say, for every Gears install via FF that also patches IE, some extra dough for MoFo).</p>
<p>It&#8217;s insane that MoFo isn&#8217;t chasing down all the angles here.</p>
<p>Regards</p>
<p><b>Update:</b> changed the language to more accurately reflect what I meant to say.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Neuberg</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235101</link>
		<dc:creator>Brad Neuberg</dc:creator>
		<pubDate>Tue, 02 Sep 2008 19:50:48 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235101</guid>
		<description>An interesting thing about Flash and users installing plugins: even though Flash has an autoupdate mechanism, I&#039;ve heard from Flash folks that most of the version upgrade happens almost entirely by users choosing to upgrade! This happens because content authors choose to use the new features, which drives demand, which drives users to flip their plugin version faster. So good content and user demand can cause plugins to have growth. 

BTW, much of the &#039;received wisdom&#039; about plugins was created in the late 90s, when bandwidth was slow and users were actually more conservative. Users in general are much more comfortable with the web, machines are faster, and bandwidth is much easier to download a plugin that might be several megabytes. In addition, the received wisdom was that plugins == proprietary in the 90s, which was true when they started. However, open source plugins like Gears changes this equation. If plugins are an effective way to help induce change on the web, why not use them to get some more movement going?

Best,
  Brad
  Google Open Web Advocate</description>
		<content:encoded><![CDATA[<p>An interesting thing about Flash and users installing plugins: even though Flash has an autoupdate mechanism, I&#8217;ve heard from Flash folks that most of the version upgrade happens almost entirely by users choosing to upgrade! This happens because content authors choose to use the new features, which drives demand, which drives users to flip their plugin version faster. So good content and user demand can cause plugins to have growth. </p>
<p>BTW, much of the &#8216;received wisdom&#8217; about plugins was created in the late 90s, when bandwidth was slow and users were actually more conservative. Users in general are much more comfortable with the web, machines are faster, and bandwidth is much easier to download a plugin that might be several megabytes. In addition, the received wisdom was that plugins == proprietary in the 90s, which was true when they started. However, open source plugins like Gears changes this equation. If plugins are an effective way to help induce change on the web, why not use them to get some more movement going?</p>
<p>Best,<br />
  Brad<br />
  Google Open Web Advocate</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Privacy Place &#187; Google&#8217;s New Browser: Chrome</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235100</link>
		<dc:creator>The Privacy Place &#187; Google&#8217;s New Browser: Chrome</dc:creator>
		<pubDate>Tue, 02 Sep 2008 19:45:28 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235100</guid>
		<description>[...] is difficult to predict what sort of impact Chrome will have on the browser market, web application development, or Internet privacy, but if Chrome will have any impact, then it must compete with the &#8220;big [...]</description>
		<content:encoded><![CDATA[<p>[...] is difficult to predict what sort of impact Chrome will have on the browser market, web application development, or Internet privacy, but if Chrome will have any impact, then it must compete with the &#8220;big [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Neuberg</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235099</link>
		<dc:creator>Brad Neuberg</dc:creator>
		<pubDate>Tue, 02 Sep 2008 19:42:40 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235099</guid>
		<description>Just to add what Alex wrote about Gears, if you notice Gears and HTML 5 have been revving very fast against each other. Not only can Gears get new features across the existing installed base of the web (including IE), but those features are migrating into small standards that are vetted by the wider community. For example, Gears 0.4 just launched with a Geolocation API. The team then worked to write this up into a short spec, submitted it to the W3C, and its being revved by several others. Firefox 3.1 is planning to implement this spec, as far as I know. This is a good example of Gears, HTML 5, and web browsers working together to rapidly innovate and do standardization work (plus get actual shipping code for developers to use!).

Best,
  Brad Neuberg
  Google Open Web Advocate</description>
		<content:encoded><![CDATA[<p>Just to add what Alex wrote about Gears, if you notice Gears and HTML 5 have been revving very fast against each other. Not only can Gears get new features across the existing installed base of the web (including IE), but those features are migrating into small standards that are vetted by the wider community. For example, Gears 0.4 just launched with a Geolocation API. The team then worked to write this up into a short spec, submitted it to the W3C, and its being revved by several others. Firefox 3.1 is planning to implement this spec, as far as I know. This is a good example of Gears, HTML 5, and web browsers working together to rapidly innovate and do standardization work (plus get actual shipping code for developers to use!).</p>
<p>Best,<br />
  Brad Neuberg<br />
  Google Open Web Advocate</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajaxian &#187; Google Chrome, Chromium, and V8</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235095</link>
		<dc:creator>Ajaxian &#187; Google Chrome, Chromium, and V8</dc:creator>
		<pubDate>Tue, 02 Sep 2008 17:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235095</guid>
		<description>[...] Russell also has some good thoughts on the importance of Chrome, and Christopher Blizzard (Mozilla) also has some thoughts on how this shows the browser market is [...]</description>
		<content:encoded><![CDATA[<p>[...] Russell also has some good thoughts on the importance of Chrome, and Christopher Blizzard (Mozilla) also has some thoughts on how this shows the browser market is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235094</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Tue, 02 Sep 2008 16:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235094</guid>
		<description>Matt:

Not sure I understand your comment...the Chrome comic talks a LOT about their plugin infrastructure, and the plugin API across browsers is pretty much settled science. Are you referring to Firefox&#039;s lighter-weight extensions mechansim? If so, that is very much up in the air as far as anyone can tell. Should be interesting = )

Aaron:

Adobe had a distribution deal with Microsoft to include Flash with Windows up until a year or two ago (Vista and OEM XP&#039;s no longer include it, but the bootstrap is done).

Regards</description>
		<content:encoded><![CDATA[<p>Matt:</p>
<p>Not sure I understand your comment&#8230;the Chrome comic talks a LOT about their plugin infrastructure, and the plugin API across browsers is pretty much settled science. Are you referring to Firefox&#8217;s lighter-weight extensions mechansim? If so, that is very much up in the air as far as anyone can tell. Should be interesting = )</p>
<p>Aaron:</p>
<p>Adobe had a distribution deal with Microsoft to include Flash with Windows up until a year or two ago (Vista and OEM XP&#8217;s no longer include it, but the bootstrap is done).</p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Wilcox</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235093</link>
		<dc:creator>Matt Wilcox</dc:creator>
		<pubDate>Tue, 02 Sep 2008 12:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235093</guid>
		<description>If Chrome doesn&#039;t have a plug-in capability, then it will simply be a two-bit player. The one thing that really separates Firefox from any of the other browsers, and that elevates it from &#039;good secure browser&#039; to &#039;indispensable tool&#039;, is the plug-ins available for it.

Firefox without plugins is great, but not really anything special. Firefox with the plugins I want is light-years ahead of the competition, because it&#039;s the plugins that make it relevant to me. Chrome needs an open plug-in architecture.</description>
		<content:encoded><![CDATA[<p>If Chrome doesn&#8217;t have a plug-in capability, then it will simply be a two-bit player. The one thing that really separates Firefox from any of the other browsers, and that elevates it from &#8216;good secure browser&#8217; to &#8216;indispensable tool&#8217;, is the plug-ins available for it.</p>
<p>Firefox without plugins is great, but not really anything special. Firefox with the plugins I want is light-years ahead of the competition, because it&#8217;s the plugins that make it relevant to me. Chrome needs an open plug-in architecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235089</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Tue, 02 Sep 2008 09:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235089</guid>
		<description>Dean:

As I understand it, flash did not achieve the majority of its ubiquity through distribution deals. It got there because people wanted to see the whizzy animations, games, and other stuff they needed flash to.</description>
		<content:encoded><![CDATA[<p>Dean:</p>
<p>As I understand it, flash did not achieve the majority of its ubiquity through distribution deals. It got there because people wanted to see the whizzy animations, games, and other stuff they needed flash to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Edwards</title>
		<link>http://infrequently.org/2008/09/the-importance-of-chrome/comment-page-1/#comment-235088</link>
		<dc:creator>Dean Edwards</dc:creator>
		<pubDate>Tue, 02 Sep 2008 08:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=747#comment-235088</guid>
		<description>I&#039;m, saying that people don&#039;t install plugins. Period. Flash is the exception because it is *pre-installed* on most machines. I thought you knew that.</description>
		<content:encoded><![CDATA[<p>I&#8217;m, saying that people don&#8217;t install plugins. Period. Flash is the exception because it is *pre-installed* on most machines. I thought you knew that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

