nah
Save Google Wave
11–20 of 65 posts
Re: Save Google Wave
#12Many of the problems wave aimed to remedy still stand. It's my hope that google will bow out gracefully, leaving behind the work they have done and allow other to pick up where they left off. This seems to be the plan, although they haven't open sourced the entirety of the effort.
Re: Save Google Wave
#13The 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 browser are you using? Loads in less than a second for me. The interface doesn't seem any more complicated than a hackernews comment thread.
Firefox 3.6, Linux, 4 gigs of RAM, 1.86 ghz CPU, 10 mbit connection.
9 second load time. And the scrollbar is uselessly broken. (Nonstandard behavior, arrow keys don't work, etc)
Re: Save Google Wave
#14[Wait several minutes for a large complex unwieldy UI to load]
at the time I went it had 300+ people in the wave and over 170 threads; above what I suspect was the average user case; try loading a regular wave.. with less than 20 people and its good to go. (use chrome if you can also; its faster.)
Re: Save Google Wave
#15I 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.
Re: Save Google Wave
#16Earlier quoted context omitted.
What browser are you using? Loads in less than a second for me. The interface doesn't seem any more complicated than a hackernews comment thread.
I think you're being disingenuous, or just trying to get a rise out of people. There's little debate on these points, it was slow and the UI was unnecessarily complex. Whether or not it should be killed remains a valid topic of discussion.
I was talking about the same thing the parent was talking about. The page linked in this submission. Why are you talking in the past tense?
Re: Save Google Wave
#17Earlier quoted context omitted.
What browser are you using? Loads in less than a second for me. The interface doesn't seem any more complicated than a hackernews comment thread.
Firefox 3.6, Linux, 4 gigs of RAM, 1.86 ghz CPU, 10 mbit connection. 9 second load time. And the scrollbar is uselessly broken. (Nonstandard behavior, arrow keys don't work, etc)
Not that this is really a defense of the product, but you should try it in chrome. You'll have a better experience.
Re: Save Google Wave
#18#savewave
Re: Save Google Wave
#19I know the protocol is a bit complicated, but didn't they say a while back they're going to open source a reference implementation of the server? Is this it?: http://code.google.com/p/wave-protocol/ I do not know if that's a complete Wave server, or if it's missing a piece. But if it is a complete Wave server, there's nothing to "save". It's already been saved. You just need to run it yourself, and possibly support f…
What people want to "save" is Google's backing, proselytization, and continued investment into the project. The demand was never there—because Google never gave Wave a big marketing push, the way they did with, say, Chrome (no Wave TV commercial?) Wave is a new and unadopted protocol, and as such it won't grow organically; it needs a big company to force it down people's throats. People want to "save" the unfulfilled (implicit) promise that Google was going to be that company.
Re: Save Google Wave
#20The 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.
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.