I am assuming this is serious. Would like to see some official
confirmation of exactly what this means, maybe on an official web page
somewhere. For all I know it could be a hoax.

On 5 August 2010 09:11, Ronald C.F. Antony <ronald.ant...@gmail.com> wrote:
> This is a real travesty. To cancel Wave due to lack of adoption is pretty 
> short-sighted.

You can't expect people to change their habits overnight.

> Wave wasn't fully developed, it needed better integration with legacy
> tools like e-mail, and it needed a fully functional open sourced platform
> such that federation would be possible. Without these, to hope for mass
> adoption is foolish, and without mass adoption of course, the expected
> success will remain a dream.

For me the big issue right now is that I purchased an Android phone,
and cannot access Wave on it. So I have used protocols like XMPP
simply because they are more accessible.

However, even if this was not an issue, changing to something
radically different like wave is always going to be a slow process
while people learn how to best make use of the new technology. People
are just too comfortable with current technology (including
limitations).

Another issue, as others have said, is that Google have been
relatively slow to release the open source code - delays in doing so I
think have meant people have lost interest while waiting for this to
occur (for me I just have too many interesting projects - I can't keep
up with all of them). As a result, the decision to end it seems to
have been made before one of the major selling features was realized.

Maybe they seriously underestimated the selling power of making it
open source? As such it wasn't given the priority it deserved? If
everything was open source from day 1, I think it would have generated
a lot more serious long term interest, even if there were problems
with the code.

I feel I could have got more people interested if I could have
installed a server at work. However more people using it at work, I
think would have meant more people using Google's server.
Unfortunately I could not use it in my work environment, because my
company would be nervous about putting private company data on
Google's servers.

I don't know what the future is of Google's Wave server is now, but if
it is ever going to be shut down, the people who were nervous about
putting data on Google's servers will say they were right. In fact
they are probably already saying there were right. Especially as Wave
meant to be a released product (IIRC).

I also hope that Google will now open source the code, so wave can
continue outside of Google. I fear though that Google will not want to
on grounds that the code contains confidential information that cannot
be released, which in turn may kill the community efforts.
-- 
Brian May <br...@microcomaustralia.com.au>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Wave API" group.
To post to this group, send email to google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.

Reply via email to