3 ms·

I'm surprised at this sentiment. Could you elaborate by any chance? The reason for my surprise is because a significant portion of the Wave code base is geared

by tav 16y ago

I'm surprised at this sentiment. Could you elaborate by any chance? The reason for my surprise is because a significant portion of the Wave code base is geared around the user interface — which was, in many ways, the least attractive aspect of Wave (at least from the experiences of those I've spoken to). The other main parts of Wave were the various Operational Transform work — which, again, to my understanding from those who have looked at the OT framework released by Google last year, is inherently hard to scale up. I had always assumed that these and the general market disinterest to be the reasons that Google had abandoned the Wave project — so am very keen to understand why you would be so excited... thanks!

sushrutbidwai 16y ago
Because it will keep the hosted google wave servers maintained and enhanced? Wave may not be very useful as a user facing web app, but I really like it as an enterprise app, makes collaboration much easier between distributed teams.
oscilloscope 16y ago
The Wave-in-a-Box interface is quite barebones. Having to hack together something different in GWT is a pain though. The big advantage is the Federation protocol. Not only do you get OT between users, but between servers as well. You also get existing gadgets/robots functionality. With Federation, there will be alternate Wave server implementations to choose from. I'm working with creator of lightwave to develop a very different interface: https://code.google.com/p/lightwave/ https://code.google.com/p/lightwave/ And here are some of the UI concepts: http://fleetinbeing.net/tensor-v1/ http://fleetinbeing.net/tensor-v1/ (miller columns for long, deeply nested waves. the top and bottom bars are totally unresolved, and will probably get cut) http://fleetinbeing.net/tensor-notes-v1/ http://fleetinbeing.net/tensor-notes-v1/ (more intuitive inline-replies) If anyone has suggestions, I'd love to hear 'em. I've been trawling HN for critiques of Wave's UI.

by tav 16y ago

sushrutbidwai 16y ago

Because it will keep the hosted google wave servers maintained and enhanced? Wave may not be very useful as a user facing web app, but I really like it as an enterprise app, makes collaboration much easier between distributed teams.

oscilloscope 16y ago

The Wave-in-a-Box interface is quite barebones. Having to hack together something different in GWT is a pain though. The big advantage is the Federation protocol. Not only do you get OT between users, but between servers as well. You also get existing gadgets/robots functionality. With Federation, there will be alternate Wave server implementations to choose from. I'm working with creator of lightwave to develop a very different interface: https://code.google.com/p/lightwave/ https://code.google.com/p/lightwave/ And here are some of the UI concepts: http://fleetinbeing.net/tensor-v1/ http://fleetinbeing.net/tensor-v1/ (miller columns for long, deeply nested waves. the top and bottom bars are totally unresolved, and will probably get cut) http://fleetinbeing.net/tensor-notes-v1/ http://fleetinbeing.net/tensor-notes-v1/ (more intuitive inline-replies) If anyone has suggestions, I'd love to hear 'em. I've been trawling HN for critiques of Wave's UI.