9 second load time. And the scrollbar is uselessly broken. (Nonstandard behavior, arrow keys don't work, etc)
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 from Google for exporting your data once. If it isn't, maybe some people will fill in the blanks. If nobody steps forward to fill in the blanks then the demand probably wasn't there in the first place.
If a company like Google is not going to invest in such technologies who will. This makes me think if Google is turning into a company which jumps on to a bandwagon once it starts rolling rather than be a creator of new ideas and technologies.
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.
They know a small but loyal following uses wave. They are shutting down because that wasn't what they had in mind for wave. They were aiming big and failed. That's ok, but only if it doesn't continue to drain from the company.
(Disclaimer: I'm a Novell employee but I don't speak for them).
- 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.
Further, I'll argue that since Google effectively took away our common, central access to the EtherPad service (even though the source code remains), they in some sense "owe" the community the effort of giving Wave more of a shot -- although I expect a common response will be that "business doesn't owe you anything that doesn't make money (in an legal fashion)".
My other comments (e.g. interface, lack of documentation and post-launch publicity) are here:
