Live data from Hacker News

Turning the tide: a hands-on look at Google's Wave by Ars Technica

arstechnica.com

11–14 of 14 posts

Re: Turning the tide: a hands-on look at Google's Wave by Ars Technica

#11
post #3

I haven't been following the Wave hype, but by the end of the rather verbose first page I still had no real idea what Wave is supposed to be or why I'd want to use it. Best I can tell it's some mish-mash of email/IM/docs - which frankly sounds horrifying.

As I understand it Wave core principle is actually simple. When you do email, the fundamental unit of communication is the email. In Wave, the fundamental unit of communication is the conversation.

Unlike physical mail, most emails don't stand alone. They are part of a conversation. Conversations can get quite complicated. In mailing lists, they often get very long, effectively taking the shape of an HN thread.

Now, plain email is a mish-mash of message/IM/docs. We already use it these ways. Wave, by being very permissive, make these tasks easier. Single messages aren't harder, ML-like conversations have an enforced structure (easier to follow), and the collaborative editing thing just emerge from the possibility of modifying the entire conversation.

I see Wave like I see Lisp: a simple and consistent core, which allow many possibilities.

Re: Turning the tide: a hands-on look at Google's Wave by Ars Technica

#12
post #10
post #2

> Wave is designed to facilitate real-time concurrent messaging, meaning that content appears to all users immediately and multiple users can edit and submit content at the same time. One of the things I like about email is that it is not real-time.

Real-time just means that you can start ignoring it immediately, instead of waiting whole seconds for it to arrive in your inbox first.

If you have someone typing away on the other end and they know you're there, that's IM, and that's ok in some situations, but not in others.

Re: Turning the tide: a hands-on look at Google's Wave by Ars Technica

#13
post #3

I haven't been following the Wave hype, but by the end of the rather verbose first page I still had no real idea what Wave is supposed to be or why I'd want to use it. Best I can tell it's some mish-mash of email/IM/docs - which frankly sounds horrifying.

I was in the same situation and then I watched the video, which explains Wave quite well. Seriously, watch the video.

http://www.youtube.com/watch?v=p6pgxLaDdQw

Re: Turning the tide: a hands-on look at Google's Wave by Ars Technica

#14
post #12
post #10

Earlier quoted context omitted.

Real-time just means that you can start ignoring it immediately, instead of waiting whole seconds for it to arrive in your inbox first.

If you have someone typing away on the other end and they know you're there, that's IM, and that's ok in some situations, but not in others.

You can hide the fact that you're editing a reply until you send it, so it can act more like email, if you like.
Post reply on HN