Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> On the bright side, I feel pretty confident that some real startup will take the open sourced Wave technology and do something good...

I don't share your confidence. Making even trivial changes to the 350k lines of opensourced java takes a lot of time and a lot of skill. There are only ~5 part time developers working on it. I doubt that it will be useful anytime soon.

[Disclaimer: Some of that code is mine]



Sounds like it would almost be easier to start from scratch with the protocol spec and build something lighter weight and not Java.

Then in the client only expose a subset of features until they are really good, then another, then another. Keeping the client codebase small as well.


I agree, although if I had the chance I would change the protocol spec too.

The client-server protocol uses protobufs encoded over JSON, and the federation protocol uses protobufs encoded over XML, via an XMPP extension. As others have said, there weren't accepted standards for this stuff just a few years ago. Today, you could build whip something together reasonably easily using JSON and socket.io or something.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: