Wave Rocks and Sucks because...

So I was playing with wave and I was actually able to delete a few people's conversations... Sorry! I really didn't mean to... *sigh*

While perusing a waves I came across one named Discoveries and Observations about Wave and it's worth sharing with the rest of the world. Personally, I can see why some people love wave but I don't see it being all that and a bag of chips the way it is right now.


  • The pattern of write-reply communication is rampant in today's internet software solutions. Blogs, forums, chat, social sites, the classic "guest book", etc. are all write-reply patterns. Wave builds on this pattern while leveraging today's browser technologies and the user's higher bandwidth connection to both consolidate these technologies into an open platform for real-time, social communication.
  • Mixing realtime IM/Threading/document-collaboration is a great idea.
Aug 2
Mario Viviani:
in my opinion Wave is going to be the Super-Social Network. I mean that this stream-oriented flux of informations will obviously be used to share "social" informations. Think about organizing a meeting with your friends using Wave: it's much less complicated than using Facebook or Twitter.. With wave it's easier discuss about a video or a link.. In this way, i think Wave is going to be super-used by actual Social Network users.

Aug 2
Mickael Faivre-Ma├žon:
right now, facebook is easier than wave.... I don't see wave as a social network thingy.

  • Wave as an open standard will revolutionise the interwebs.
  • Wave can become a platform to collaborate and communicate in for other applications.
  • Can make other applications easily accessible over the web in standardized way.

Aug 1
Omar Balbuena:
I see. I don't understand what is being standardized though. Maybe user credentials?
I just find it weird to see "new features" and "standardization" in the same sentence, it's an oxymoron and it still doesn't make sense to me. Familiar interface maybe?

  • Having multiple people working on one document will decrease work time ten-fold!
  • Seeing exactly what people are working on will save time.
  • Will remove necessity of having multiple communication platforms (im, e-mail, forums, letters, smoke signals)
  • You can read while they are typing, conversations become much quicker.
  • It puts almost no constraints in how you shape communication at any point in time (an email can become a conversation can become a chat can become a document can become a game)


  • Robots can fundamentally break the wave experience (e.g. groupy)
  • And there is currently no way of removing ones that you add.
  • Permissions and wave management (kicking people etc...) are currently too limited
  • It's bewildering; I can't see the things that are interesting to me or get rid (easily or obviously) of the things that I don't care about
  • Difficult to give priority to different waves. Some may need attention more than others.
  • Wave is more complicated than alternatives such as email/forums etc... It risks alienating the less technically capable.
  • Needs more visual cues for when/where other editors are when editing the wave document.
  • Needs more server CPU added in current dev preview :)
  • Puts a lot of stress on the Javascript engine (currently works better using v8, no surprise there)
  • Though when Wave becomes an open standard, we can hope to see non-browser implementations also
  • No chrome on Mac yet, so can't test... http://www.google.com/chrome/intl/en/eula_dev.html?dl=mac go download it :D
  • I tested Wave in MacOS Chrome and it crashed after 2 min. Too early for the transation weight of Wave
  • Refactoring threaded conversations is painful with the existing wave client.
  • Drag/drop restructuring of threads and easier deletion of wavelets would be handy (via a keyboard shortcut).
  • It may be difficult to get wide adoption because people will have to learn something new, and that in turn may significantly decrease usefulness of the platform.
  • Feels wrong, in such an application-like environment, to not have right click menus
  • Too hard to see who has edited what.
  • it hammers the hell out of my firefox
  • it's difficult to see when it's doing something, like is it fetching data or just sleeping. Feels like it needs a progress bar
  • It puts almost no constraints in how you shape communication at any point in time (you never know what you are supposed to be doing)
Jul 31
Omar Balbuena:
I don't see why that is bad.

Jul 31
Anton Babushkin:
Having no clear direction is always bad, especially for those who are simply "meh" and don't want to put too much thought into things (i.e. your regular user)

  • Is essentially a new type of mail, yet, isn't backwards compatible (e.g. being able to send emails with it would be useful for those without wave)
  • Much information is lost when the wave turns into a rant, could be a problem for longer waves.
  • Can't get to the newest item in a Wave easily. When there's lots of items, it would be convinient for a keyboard shortcut (left arrow?) to go to the newest item, which may, in some cases, not be the bottom.
  • I don't like scroll bars but I don't like that my cursor keys don't work line at a time. They're more like page keys. Fine on the small entries but entries like this one that are bigger than a page, it fails badly.
  • I hate to scroll back to find edit/reply button when the comment is too long. ditto 'done' button at bottom.
  • The search isn't good enough. If I was adding someone called "Fred" to a Wave, and my criteria was "fred" then it wouldn't find "Fred"
  • Hard to see what's new in a wave when there has been a lot of edits
  • Navigation (e.g. the center list of waves, content on the right) is a little archaic feeling.

Thank you Dion Hinchcliffe for starting this wave. I agree with most of your points.