41–50 of 65 posts
Earlier quoted context omitted.
Do people really think like this?
It wasn't obvious to me what it was for or how to use it, no-one I knew personally was using it, and I don't have the free time to casually learn an entire new paradigm to do... whatever it was you did with Wave.
I do think the announcement to kill it off was a bit early :( - I use wave daily and have for a while for basic 'group meetings' with people who work remote. I am also surprised that Google didn't keep it alive for internal use (where Gmail came from) ~ perhaps they have something entirely new in the pipe.
Earlier quoted context omitted.
It wasn't obvious to me what it was for or how to use it, no-one I knew personally was using it, and I don't have the free time to casually learn an entire new paradigm to do... whatever it was you did with Wave.
How can you say 'no big loss' just because you personally didn't find it useful?
New products fail all the time. When the company making the product fails to even explain what the product does and just heaps buzzwords together I don't feel any sense of loss when the product goes away. This wouldn't even be newsworthy if it wasn't Google behind it.
The ridiculously confusing interface to the Wave loaded on this page, plus the fact that it takes 30 seconds to load and then runs like a dog, is the perfect explanation of why Wave is being shut down. It's almost like that's what they were trying to demonstrate.
The ridiculously confusing interface to the Wave loaded on this page, plus the fact that it takes 30 seconds to load and then runs like a dog, is the perfect explanation of why Wave is being shut down. It's almost like that's what they were trying to demonstrate.
What are you talking about? I'm using Chrome and it seems like the page has loaded, but all I see is the , , "If you think..." and thumbs up button (plus the spread the word stuff on the bottom). Am I supposed to see a link to a Wave embedded in the page?
Earlier quoted context omitted.
You’re confusing Wave and Google Wave. Google killing Google Wave essentially kills Wave as a whole, at this point; we all think Google’s web-client sucked fucking balls, but there’s not much we could do about that. What matters is that Google killing their shitty client, along with their back-end provider, also kills the ecosystem, because it’s so young.
I could really care less if google killed their own hosting of Wave servers. That's never what I was interested in anyway. A ubiquitous messaging federated service as an alternative to email? Now that's what I was looking forward too and simply never materialized. Where's the download link at google.com to a Wave Server with a much simpler Wave client I can run on my own servers?
Your mom is a ubiquitous messaging federated service.
I do think the announcement to kill it off was a bit early :( - I use wave daily and have for a while for basic 'group meetings' with people who work remote. I am also surprised that Google didn't keep it alive for internal use (where Gmail came from) ~ perhaps they have something entirely new in the pipe.
I'd bet that lack of internal adoption is 50% of the equation here.
The most obvious feature Google should have invested 5,000 man hours in: making Wave seamless in GMail as a standard. If you are talking to another GMail user, Wave should be automatically turned on for that message. I do not understand why this wasn't deathly obvious to them from the day that they announced Wave at Google IO 2009.
I don't know enough about internal Google to really say whether this is probable or not, but I've worked for companies where that would have been the case.
I never found out what Google Wave was for, so it is really not a big loss.