Well, I am not sure it's the right place to discuss about this - hence
I cannot find other place to talk about this new, shinning, shock
idea, and the implementation, Google Wave.
Google Wave (and the Wave Protocol), indicates that the email era is
ending.
Why?
1. Email has been used for more than 50 years. That time, people use
it because network infrastructure is not as advanced as today, so they
need a delayed, some sort of 'replicate/wait/send' based usage
behaviour. But now it's totally different. You, you and you, check
your cooperate email. How much usage of your email? how many times you
open up an email and there is only one Yes/No? how many times you/your
collegue use email to collect feedback? Its not information, it's some
times noise.
Today, both the network infrastructure, and the user behavior is ready
to accept a new type of collobration environment. Twitter is. Facebook
is. And now, the Wave.
2. I am a technical person, with 9+ programming experience. I've
suffered especially working out customized application on Lotus Notes/
Exchange platform. The world is calling for a new, open standard
platform for creating customized applications. Have you ever use email
collecting feedback? do voting? or use something else? Wave give a
possbility (and it's true) that you can create/reuse open techlogies
and embed them inside one workbench!
I can see that, after 5-10 years, cooperation will setup Wave Server
instead of Email server; people will print wave ID instead of email
address; Email will be considered as legacy, so there are companies
make profit on this migration business.
we will not have multiple copies of a message sitting in our inbox &
we breaking our head over them...
conventionaly email replies are either answers to the questions to the
previous email or suggestions and ideas...wave will provide an
accurate mechanism to share your opinion on each topic in the mail...
with robots and plugins oppertunities are enormous...
games,documentation etc as shown in the presentation...
education,research are other areas which could benefit from this
platform...
On May 29, 10:51 pm, Michael Chen <mechil...@gmail.com> wrote:
> Well, I am not sure it's the right place to discuss about this - hence
> I cannot find other place to talk about this new, shinning, shock
> idea, and the implementation, Google Wave.
> Google Wave (and the Wave Protocol), indicates that the email era is
> ending.
> Why?
> 1. Email has been used for more than 50 years. That time, people use
> it because network infrastructure is not as advanced as today, so they
> need a delayed, some sort of 'replicate/wait/send' based usage
> behaviour. But now it's totally different. You, you and you, check
> your cooperate email. How much usage of your email? how many times you
> open up an email and there is only one Yes/No? how many times you/your
> collegue use email to collect feedback? Its not information, it's some
> times noise.
> Today, both the network infrastructure, and the user behavior is ready
> to accept a new type of collobration environment. Twitter is. Facebook
> is. And now, the Wave.
> 2. I am a technical person, with 9+ programming experience. I've
> suffered especially working out customized application on Lotus Notes/
> Exchange platform. The world is calling for a new, open standard
> platform for creating customized applications. Have you ever use email
> collecting feedback? do voting? or use something else? Wave give a
> possbility (and it's true) that you can create/reuse open techlogies
> and embed them inside one workbench!
> I can see that, after 5-10 years, cooperation will setup Wave Server
> instead of Email server; people will print wave ID instead of email
> address; Email will be considered as legacy, so there are companies
> make profit on this migration business.
Collaboration and shared waves is probably one of the most useful and basic
concepts!
Allowing a user to proceedurally respond to chunks of a message body and
have anyone else view and also collaborate to that end is one of the most
important uses in my opinion.
On Sat, May 30, 2009 at 8:06 AM, axnchat <axnc...@gmail.com> wrote:
> we will not have multiple copies of a message sitting in our inbox &
> we breaking our head over them...
> conventionaly email replies are either answers to the questions to the
> previous email or suggestions and ideas...wave will provide an
> accurate mechanism to share your opinion on each topic in the mail...
> with robots and plugins oppertunities are enormous...
> games,documentation etc as shown in the presentation...
> education,research are other areas which could benefit from this
> platform...
> On May 29, 10:51 pm, Michael Chen <mechil...@gmail.com> wrote:
> > Well, I am not sure it's the right place to discuss about this - hence
> > I cannot find other place to talk about this new, shinning, shock
> > idea, and the implementation, Google Wave.
> > Google Wave (and the Wave Protocol), indicates that the email era is
> > ending.
> > Why?
> > 1. Email has been used for more than 50 years. That time, people use
> > it because network infrastructure is not as advanced as today, so they
> > need a delayed, some sort of 'replicate/wait/send' based usage
> > behaviour. But now it's totally different. You, you and you, check
> > your cooperate email. How much usage of your email? how many times you
> > open up an email and there is only one Yes/No? how many times you/your
> > collegue use email to collect feedback? Its not information, it's some
> > times noise.
> > Today, both the network infrastructure, and the user behavior is ready
> > to accept a new type of collobration environment. Twitter is. Facebook
> > is. And now, the Wave.
> > 2. I am a technical person, with 9+ programming experience. I've
> > suffered especially working out customized application on Lotus Notes/
> > Exchange platform. The world is calling for a new, open standard
> > platform for creating customized applications. Have you ever use email
> > collecting feedback? do voting? or use something else? Wave give a
> > possbility (and it's true) that you can create/reuse open techlogies
> > and embed them inside one workbench!
> > I can see that, after 5-10 years, cooperation will setup Wave Server
> > instead of Email server; people will print wave ID instead of email
> > address; Email will be considered as legacy, so there are companies
> > make profit on this migration business.
I'm sure email will still have its place for a long, long time -- even
if wave will do what email does better than email does it. It's
ingrained into the fabric of networking and the web. Analogously, half
the world has a cell phone, but the phone lines aren't going to be cut
anytime soon.
However, wave could be the end of email for the smarter of us! We'll
see...
Since your wave ID is the same as your email id, if you have a email
gateway, it would be trivial to manage email inside a Wave client. A Wave
can always be reduced to a bunch of emails.
Btw, I'm orgainizing a google wave discussion lunch tomorrow (5/31)
www.socializr.com/event/976099347 If you are from the area, it would be
great if you can come by so that we can discuss further how email can
coexist in a Wave world.
On Sat, May 30, 2009 at 3:19 PM, SEH <codr...@gmail.com> wrote:
> I'm sure email will still have its place for a long, long time -- even
> if wave will do what email does better than email does it. It's
> ingrained into the fabric of networking and the web. Analogously, half
> the world has a cell phone, but the phone lines aren't going to be cut
> anytime soon.
> However, wave could be the end of email for the smarter of us! We'll
> see...
> Analogously, half the world has a cell phone, but the phone lines aren't going to be cut
anytime soon.
I saw that bleeper has disappear for near 8 years, as right after cell
phone appear. There is a requirement in this time that people require
realtime, more efficient communication tool and Wave is. I don't see
any more value email provided than Wave.
> it would be trivial to manage email inside a Wave client
That's what I mean - there will be a business exists for a while, for
helping company migrate from email to wave. As far as I see, it could
be a Robot, just like twitter. There should be no conflict between a
wave id and email address even though there are the same, as they are
using different protocol. A email robot can observe a POP3/IMAP
account and synchronize into Wave.
On Sun, May 31, 2009 at 6:19 AM, SEH <codr...@gmail.com> wrote:
> I'm sure email will still have its place for a long, long time -- even
> if wave will do what email does better than email does it. It's
> ingrained into the fabric of networking and the web. Analogously, half
> the world has a cell phone, but the phone lines aren't going to be cut
> anytime soon.
> However, wave could be the end of email for the smarter of us! We'll
> see...
On May 30, 10:45 pm, Michael Chen <mechil...@gmail.com> wrote:
> > it would be trivial to manage email inside a Wave client
> That's what I mean - there will be a business exists for a while, for
> helping company migrate from email to wave.
Seems to me the bigger hurdle will be managing waves in email clients
-- early adopters of Wave will need to wait months and years for some
people to start using it, and we'll need to include wave and non-wave
users in conversations (waves? wavelets?). I expect one of the most
valuable extensions to encourage adoptions will translate wave
activity into email or discussion list format.
|
