Comments on: Google Wave: Tsunami or Microwave? The Q&A http://redmonk.com/sogrady/2009/06/17/google-wave/ because technology is just another ecosystem Sun, 13 May 2012 00:23:29 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Google Buzz in Google Buzz – Quick Analysis http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-591421 Google Buzz in Google Buzz – Quick Analysis Thu, 11 Feb 2010 17:03:03 +0000 http://redmonk.com/sogrady/?p=2831#comment-591421 [...] were early hopes among us RedMonks that Google Wave’s big deal would be as some API/data center. The protocol was going to be thing. The problem with Wave was [...] [...] were early hopes among us RedMonks that Google Wave’s big deal would be as some API/data center. The protocol was going to be thing. The problem with Wave was [...]

]]> By: Coté's People Over Process » Google Buzz in Google Buzz – Quick Analysis http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-591390 Coté's People Over Process » Google Buzz in Google Buzz – Quick Analysis Thu, 11 Feb 2010 15:01:34 +0000 http://redmonk.com/sogrady/?p=2831#comment-591390 [...] were early hopes among us RedMonks that Google Wave’s big deal would be as some API/data center. The protocol was going to be thing. The problem with Wave was [...] [...] were early hopes among us RedMonks that Google Wave’s big deal would be as some API/data center. The protocol was going to be thing. The problem with Wave was [...]

]]> By: John Doe http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-553485 John Doe Sun, 21 Jun 2009 02:13:10 +0000 http://redmonk.com/sogrady/?p=2831#comment-553485 IBM's Blue Spruce project investigating the "cooperative web" seems to be in the same ballpark as Wave. http://www.readwriteweb.com/archives/ibm_blue_spruce_first_look.php IBM’s Blue Spruce project investigating the “cooperative web” seems to be in the same ballpark as Wave.

http://www.readwriteweb.com/archives/ibm_blue_spruce_first_look.php

]]> By: iethnographer's status on Friday, 19-Jun-09 19:55:12 UTC - Identi.ca http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-553288 iethnographer's status on Friday, 19-Jun-09 19:55:12 UTC - Identi.ca Fri, 19 Jun 2009 19:56:24 +0000 http://redmonk.com/sogrady/?p=2831#comment-553288 [...] Restrictive perspective on "tradition" but insight on engineering approach to discontinuity. http://ur1.ca/5yoq [...] [...] Restrictive perspective on "tradition" but insight on engineering approach to discontinuity. http://ur1.ca/5yoq [...]

]]> By: People Over Process » IT Management & Cloud Podcast #43 - News Catch Up http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-553239 People Over Process » IT Management & Cloud Podcast #43 - News Catch Up Fri, 19 Jun 2009 13:45:24 +0000 http://redmonk.com/sogrady/?p=2831#comment-553239 [...] Google Wave - see also Stephen O’Grady’s take. [...] [...] Google Wave – see also Stephen O’Grady’s take. [...]

]]> By: sogrady http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-552719 sogrady Wed, 17 Jun 2009 17:45:40 +0000 http://redmonk.com/sogrady/?p=2831#comment-552719 @james governor: good catch, James. disclosure is added. @james governor: good catch, James. disclosure is added.

]]> By: james governor http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-552718 james governor Wed, 17 Jun 2009 17:39:44 +0000 http://redmonk.com/sogrady/?p=2831#comment-552718 client disclosure needed? client disclosure needed?

]]> By: Gordon Haff http://redmonk.com/sogrady/2009/06/17/google-wave/comment-page-1/#comment-552701 Gordon Haff Wed, 17 Jun 2009 15:54:20 +0000 http://redmonk.com/sogrady/?p=2831#comment-552701 Interesting look from the document perspective. One of the big questions I have about Wave from a communications perspective (and, indeed, one I have about converged communications in general) is to what degree it really makes sense to jam together different communications mechanisms given their different characteristics and uses. For example, IM is presence-aware, real-time, and less formal than email so there may be value in preserving a division between them. Or maybe not. I at least conceptually get some of the advantages of pulling everything together into one place but in practice I also see the advantages of keeping certain types of channels largely autonomous. Interesting look from the document perspective. One of the big questions I have about Wave from a communications perspective (and, indeed, one I have about converged communications in general) is to what degree it really makes sense to jam together different communications mechanisms given their different characteristics and uses. For example, IM is presence-aware, real-time, and less formal than email so there may be value in preserving a division between them. Or maybe not. I at least conceptually get some of the advantages of pulling everything together into one place but in practice I also see the advantages of keeping certain types of channels largely autonomous.

]]>