<?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"
	>
<channel>
	<title>Comments on: what&#8217;s right about Google</title>
	<atom:link href="http://www.syntheticzero.com/?feed=rss2&#038;p=828" rel="self" type="application/rss+xml" />
	<link>http://www.syntheticzero.com/?p=828</link>
	<description>art, life, philosophy, architecture, literature, film, performance, and other stuff</description>
	<pubDate>Fri, 17 Apr 2026 08:27:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: mitsu</title>
		<link>http://www.syntheticzero.com/?p=828#comment-547</link>
		<dc:creator>mitsu</dc:creator>
		<pubDate>Mon, 30 Nov 2009 00:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.syntheticzero.com/?p=828#comment-547</guid>
		<description>(As for the working on it: I'll be talking about that soon when we're a bit farther along...)</description>
		<content:encoded><![CDATA[<p>(As for the working on it: I&#8217;ll be talking about that soon when we&#8217;re a bit farther along&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mitsu</title>
		<link>http://www.syntheticzero.com/?p=828#comment-546</link>
		<dc:creator>mitsu</dc:creator>
		<pubDate>Sun, 29 Nov 2009 23:48:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.syntheticzero.com/?p=828#comment-546</guid>
		<description>I agree it's a prototype, but the problem is the prototype already has built into it a ton of limitations. The problem isn't just the UI, it's the entire conceptualization of the tool, the metaphors used, the structural assumptions. I think if there is going to be something great coming out of Wave it will simply be the idea of real-time multimedia document editing, transferred to a radically different context, with different addressing, different rules. I.e., the very "playback" concept itself, while clever, itself imposes severe restrictions on its utility... I'm not sure how a reskin could ever fix these problems.

Someday, someone might make something cool with the underlying Wave API, but likely as not someone will just start over and make the next really cool thing.</description>
		<content:encoded><![CDATA[<p>I agree it&#8217;s a prototype, but the problem is the prototype already has built into it a ton of limitations. The problem isn&#8217;t just the UI, it&#8217;s the entire conceptualization of the tool, the metaphors used, the structural assumptions. I think if there is going to be something great coming out of Wave it will simply be the idea of real-time multimedia document editing, transferred to a radically different context, with different addressing, different rules. I.e., the very &#8220;playback&#8221; concept itself, while clever, itself imposes severe restrictions on its utility&#8230; I&#8217;m not sure how a reskin could ever fix these problems.</p>
<p>Someday, someone might make something cool with the underlying Wave API, but likely as not someone will just start over and make the next really cool thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Wang</title>
		<link>http://www.syntheticzero.com/?p=828#comment-545</link>
		<dc:creator>Lawrence Wang</dc:creator>
		<pubDate>Sun, 29 Nov 2009 23:33:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.syntheticzero.com/?p=828#comment-545</guid>
		<description>Uncertainty: Getting lost is what should happen in your work, not in your tools. Having an intuitive email client doesn't constrain the process of figuring out what to say...

Wave: Wave is a crazy mess, yeah. But the key thing to keep in mind is that Wave is not finished; in fact, it's only just getting started. This is the open source development process: let the public bang on it and expose its flaws; roll out improvements; iterate.

I predict that if Wave ever takes off, it will be because people outside of Google with great design sense build an interface on top of it focused around a cohesive vision of user experience.

"I'm working on it": Do tell!</description>
		<content:encoded><![CDATA[<p>Uncertainty: Getting lost is what should happen in your work, not in your tools. Having an intuitive email client doesn&#8217;t constrain the process of figuring out what to say&#8230;</p>
<p>Wave: Wave is a crazy mess, yeah. But the key thing to keep in mind is that Wave is not finished; in fact, it&#8217;s only just getting started. This is the open source development process: let the public bang on it and expose its flaws; roll out improvements; iterate.</p>
<p>I predict that if Wave ever takes off, it will be because people outside of Google with great design sense build an interface on top of it focused around a cohesive vision of user experience.</p>
<p>&#8220;I&#8217;m working on it&#8221;: Do tell!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
