<?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>the blog @ popjack dot net &#187; Google</title>
	<atom:link href="http://blog.popjack.net/tag/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.popjack.net</link>
	<description>ramblings of a mediocre genius</description>
	<lastBuildDate>Mon, 22 Mar 2010 20:54:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Google Wave &#8212; A follow-up</title>
		<link>http://blog.popjack.net/2009/10/20/google-wave-a-follow-up/</link>
		<comments>http://blog.popjack.net/2009/10/20/google-wave-a-follow-up/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 13:32:14 +0000</pubDate>
		<dc:creator>popjack</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Wave]]></category>

		<guid isPermaLink="false">http://blog.popjack.net/?p=115</guid>
		<description><![CDATA[With invites sent, received, and a couple of actual threaded conversations under my belt, I&#8217;m now ready to share some less premature thoughts about Google Wave (VVave). Here they are, in no particular order:
* A lot of things still don&#8217;t work well, or at least not intuitively. It&#8217;s early beta, fair enough, and it&#8217;s not [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone" title="Wavescreen" src="http://www.popjack.net/images/wave.png" alt="" width="509" height="164" />With invites sent, received, and a couple of actual threaded conversations under my belt, I&#8217;m now ready to share some less premature thoughts about Google Wave (VVave). Here they are, in no particular order:</p>
<p>* A lot of things still don&#8217;t work well, or at least not intuitively. It&#8217;s early beta, fair enough, and it&#8217;s not like they didn&#8217;t warn us. But I am a little surprised at how much they&#8217;ve let go. For example, it&#8217;s tough to delete waves, or leave public waves. I don&#8217;t mean the process is physically demanding; you just drag the object to the trash, but it doesn&#8217;t always work.</p>
<p>* For a web app, it&#8217;s incredibly CPU intensive. As I type this on my netbook (Asus EEE PC 1005HAB &#8211; 1.6 GHz Intel Atom running Windows 7 w/ 2GB RAM) with one Chrome window open, my CPU usage is fluctuating between 5% and 20%. Let&#8217;s open a Wave and see what happens&#8230;</p>
<p>Ok, CPU utilization jumps to between 60% and 80%, and that&#8217;s just opening a wave &#8212; not having a threaded conversation. Why so much? Because Wave depends heavily on Gears, so your machine is doing more of the heavy lifting than it usually does for web apps, where most of the processing takes place on the server side. This also matters because Gears performance is not the same in all browsers. Since Chrome is optimized for Gears, then one could say that Wave is optimized for Chrome.</p>
<p>* Conversations in Google Wave take some getting used to, and have a lot more to do with personal preferences.  IM is real-time, and email is turn-based, (for all you strategy game nerds out there), but Wave is somewhere in-between. So I&#8217;ve chatted with one person who started a new &#8220;blip&#8221; with each response. On another chat with a different person, we kept our own blips running, so it was a chat in two separate windows.</p>
<p>Ok, I&#8217;m over my word limit, so I&#8217;m cutting off here. Lots more thoughts to follow.</p>
<p>Oh, and I still have one invite left.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.popjack.net/2009/10/20/google-wave-a-follow-up/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Google VVave: The sound of one hand clapping</title>
		<link>http://blog.popjack.net/2009/10/15/google-vvave-the-sound-of-one-hand-clapping/</link>
		<comments>http://blog.popjack.net/2009/10/15/google-vvave-the-sound-of-one-hand-clapping/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 15:12:57 +0000</pubDate>
		<dc:creator>popjack</dc:creator>
				<category><![CDATA[Culture]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://blog.popjack.net/?p=111</guid>
		<description><![CDATA[Google VVave  is a brilliant concept, with a simple summary; &#8220;Suppose email had been invented today.&#8221;
In short, Google VVave extends GMail&#8217;s concept of email as a threaded conversation rather than a string of discrete documents. VVave makes every email a collaborative conversation, that blends

traditional asynchronous discussion (I send you an e-mail, you read it whenever [...]]]></description>
			<content:encoded><![CDATA[<p>Google VVave  is a brilliant concept, with a simple summary; <em>&#8220;Suppose email had been invented today.&#8221;</em></p>
<p>In short, Google VVave extends GMail&#8217;s concept of email as a threaded conversation rather than a string of discrete documents. VVave makes every email a collaborative conversation, that blends</p>
<ul style="padding-left: 60px;">
<li><span style="background-color: #ffffff;">traditional asynchronous discussion (I send you an e-mail, you read it whenever and respond at your convenience) </span></li>
<li><span style="background-color: #ffffff;">real-time chat (we&#8217;re both on line, and we talk back and forth, within our email thread) </span></li>
<li><span style="background-color: #ffffff;">social media (where we can embed images, videos, links, etc.) </span></li>
</ul>
<p>It feels kinda like Facebook for introverts, where you might want to have a multi-media, multi-threaded conversation that evolves over time with one or a small group of users, but not leave it open to all 138 of your friends (or more, if you&#8217;re less of an introvert).</p>
<p>If you want the specifics of what it does and how it does it, I recommend watching the videos Google&#8217;s posted. They are fun and watchable and neither technical nor dumbed down.</p>
<p>I just have one problem with Google VVave, and that&#8217;s how stingy they&#8217;ve been with invites. I got my invite in the second round, and I&#8217;ve since &#8220;nominated&#8221; a few other people, none of whom have received their invites yet.</p>
<p>I understand that it&#8217;s beta, I understand that the kinks haven&#8217;t been worked out, and it was fun to be one of the first people I knew with a GMail account. But I could email anyone with my GMail account, not just other GMail users. I now have a ingenious <em>collaborative</em> tool, and no collaborators. Huh?</p>
<p>So yeah, Google VVave is brilliant, just not so&#8217;s you&#8217;d notice.</p>
<p>PS &#8212; If any readers already have VVave accounts, let me know. I&#8217;m dying to try it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.popjack.net/2009/10/15/google-vvave-the-sound-of-one-hand-clapping/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
