<?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: Thinking about Google Wave</title>
	<atom:link href="http://ginstrom.com/scribbles/2009/05/31/thinking-about-google-wave/feed/" rel="self" type="application/rss+xml" />
	<link>http://ginstrom.com/scribbles/2009/05/31/thinking-about-google-wave/</link>
	<description>Random scribbling about programming, translation, and Japan</description>
	<lastBuildDate>Fri, 03 Feb 2012 09:05:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ryan Ginstrom</title>
		<link>http://ginstrom.com/scribbles/2009/05/31/thinking-about-google-wave/comment-page-1/#comment-4567</link>
		<dc:creator>Ryan Ginstrom</dc:creator>
		<pubDate>Mon, 01 Jun 2009 05:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1096#comment-4567</guid>
		<description>That&#039;s a good point about the IE6 crowd.

Wave could be great for translators as well. Since Wave is encrypted by default, it&#039;ll be a secure way to exchange files with clients, and hopefully replace the proprietary, half-baked file servers that a lot of them seem to be adopting.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a good point about the IE6 crowd.</p>
<p>Wave could be great for translators as well. Since Wave is encrypted by default, it&#8217;ll be a secure way to exchange files with clients, and hopefully replace the proprietary, half-baked file servers that a lot of them seem to be adopting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Rice</title>
		<link>http://ginstrom.com/scribbles/2009/05/31/thinking-about-google-wave/comment-page-1/#comment-4497</link>
		<dc:creator>Adam Rice</dc:creator>
		<pubDate>Sun, 31 May 2009 18:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1096#comment-4497</guid>
		<description>I predict that if Wave takes off, it will spawn a plethora of dedicated clients, much as Twitter has. Some will be little more than site-specific browsers, some will interact with it entirely through its API using native widgets (in fact, one might go so far as to say this would be a necessary condition for judging its success). Google will also, no doubt, have a link to Chrome that gets featured prominently on its Wave site, especially when the UA is IE6.

People who are mired in IE6 probably fall into two overlapping categories: late adopters and corporate users. The former will get on board when they buy a new computer and/or when their family and friends give them a strong reason to. The latter will get on board when the IT department decides it&#039;s time. I don&#039;t think either of these groups will retard its success, any more than they have retarded the success of Twitter.</description>
		<content:encoded><![CDATA[<p>I predict that if Wave takes off, it will spawn a plethora of dedicated clients, much as Twitter has. Some will be little more than site-specific browsers, some will interact with it entirely through its API using native widgets (in fact, one might go so far as to say this would be a necessary condition for judging its success). Google will also, no doubt, have a link to Chrome that gets featured prominently on its Wave site, especially when the UA is IE6.</p>
<p>People who are mired in IE6 probably fall into two overlapping categories: late adopters and corporate users. The former will get on board when they buy a new computer and/or when their family and friends give them a strong reason to. The latter will get on board when the IT department decides it&#8217;s time. I don&#8217;t think either of these groups will retard its success, any more than they have retarded the success of Twitter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

