Damn, it's like I don't even need to write the paper at all :) Great research work, it does capture the idea of the project.

Given that this is HN, my comment probably came across as a disappointment and most people were already aware of the surface level details of caching.

Hope I kept them at least mildly entertained while waiting for the real deal to drop : )

Here's the recently updated Wiki page, it's not super in-depth, but please let me know what you think :)

A man's gotta do... The zeta stuff is coming in my white paper real soon and will be summarized in https://github.com/fed135/ha-store/wiki

Cheers :)

Thanks for the advice, figured Protobuf would speak to a broader audience.

I think the other slogan is better because it mentions what you try to do differently from protobuf, which is your selling point against protobuf (which has wider support, more language bindings, ... and thus is hard to compete with on the basis of just "we do the same")

Hey guys, I started this project, and it's now at a usable stage, but I would really enjoy some criticism and some input on how to further optimize this.

This library works in the same way as Protocol buffers do - schema-based compression of JS objects. With the twist that it doesn't rely on proto files, but rather attempts to re-use JS/JSON DB Schemas (DRY). Also, this has NO dependencies!