Hemant Shah M.D., M. Surg. |
|
Websites: |
--
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-...@googlegroups.com.
To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
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.
Wave didn't progress past the stage of being a very advanced technology demonstration for the above mentioned reasons, it's like when GM killed the electric car: it wasn't the fault of technology, but of bad strategy.
So I guess we'll be stuck with e-mail and a variety of IM "standards" for decades to come...
...all I can hope is that Google at least open-sources all the things they wrote to get Wave to this point, so maybe the community picks up and fulfills the promise of Wave.
Ronald
--
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-...@googlegroups.com.
To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
--
Wave is a good product.
If a product is bad no one remembers or mentions it. I think that this
is not the case of Wave
I'm interested in using Wave and making developments using their API
Wave +1 :-)
2010/8/4 Daniel França <daniel...@gmail.com>:
We have enough of the federation protocol and OT hammered out that it
is quite possible to build something like the Apache Foundation for
Wave. If Google wanted to come to the party with their production
server setups, it would make things so much better.
It is incredibly disappointing that Google has made this decision,
especially before investigating other options to keep development on
the tech going, but I believe it is possible to pull Wave out of the
fire, it'll just take a while.
James
On 5 August 2010 09:11, Ronald C.F. Antony <ronald...@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>
Finally some good news!
--
Brian May <br...@microcomaustralia.com.au>
Sent from my iPhone
2010/8/5 Andrés Cerezo <acerezo...@gmail.com>:
--
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-...@googlegroups.com.
To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
I still think the proper thing to do is just integrate Wave with GMail
and give more people good reasons to use GMail.
Wave is one of the best inventions since e-mail itself. It dramatically
improves how people communicate and collaborate. We just haven't been
given long enough to get familiar with it and incorporate it into our
daily lives.
Please Google - don't let Wave die.
Eric Kolotyluk
--
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-...@googlegroups.com.
To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
It kind of irritates me the way Google went about this. They started a
community effort to create something new and unique. They got this
community effort, and things seemed to be happening. When we could
start to see the light at the end of the tunnel, they decided to
cancel the project. Instead of officially informing the community via
their own discussion forums of what is happening, we first find out
via the media outlets. Even then, in their official blog, they haven't
acknowledged the contributions made by extensive community efforts -
just some vague reference to "numerous loyal fans". Its like the
community doesn't matter.
So I really think it was always seen by Google management as a
commercial/proprietary product, despite the fact it was being
advertised as a community effort. That is why it has failed.
Alternatively, Google has shown they don't know how to run a community
project.
They still haven't really explained what this announcement means. Will
people lose data they have on Google Wave?
I would hope that wave can now be forked and developed independently
of Google, with or without Google's help. First step, perhaps, should
be to stop calling it Google Wave.
Even if Google did decide to change their mind and continue running
the show (as other people seem to be suggesting), they would have to
show some serious commitment (e.g. releasing all the code as open
source). Otherwise I wouldn't be able to trust them not to do the same
thing in the future, again.
--
Brian May <br...@microcomaustralia.com.au>
To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.