The current Apache Wave code base is a vast complex tangle (GWT wasn't the right decision, I doubt web sockets was either), and there's virtually no life on the developer list.
To be in any way seriously useful, this should be reimplemented as from scratch with a strict separation of UI and wave server back end, with a massively simplified deployment process. (Go would be a good choice imho).
The ideas behind wave are interesting, but the technical debt that Google dumped out when they abandoned wave is so massive, I consider the current wave code base a completely lost cause.
Seriously; interested developers drop into the mailing list form time to time; look at the code base, then run screaming. The reports barely even get done.
I agree with this. I wanted to add OT to one of my projects and checked it out. Couldn't get the head or tail of the code. So opted for ShareJS instead.
GWT reduces complexity for this sort of thing imho - the complexity comes more from the way the client and server code are tied all together, the rather excessive abstractions and factory processes, and some legacy stuff.
GWT should be just a pretty simple client that crosscompiles nicely to browser specific, very optimised, js.
To be in any way seriously useful, this should be reimplemented as from scratch with a strict separation of UI and wave server back end, with a massively simplified deployment process. (Go would be a good choice imho).
The ideas behind wave are interesting, but the technical debt that Google dumped out when they abandoned wave is so massive, I consider the current wave code base a completely lost cause.
Seriously; interested developers drop into the mailing list form time to time; look at the code base, then run screaming. The reports barely even get done.