This definitely seems to set a new bar in terms of simplicity for integrating with a backend, which is nice, but this bit is concerning: "jindo will replay every jindo event that has occured on that website". That would presumably need to change if it were to scale beyond a small amount of history, though then I wonder if you can keep the model as simple as it is now.
Thanks for the feedback! Part of our roadmap includes "server-side" observables. This will allow state to be calculated and cached on the server side, so that clients don't have to recalculate the state of the universe every time there is a page load.
Really like the ability for a developer to instantly setup a reactive backend without having to first sign up with an API provider, receive credentials and put down a credit card. Might there be a way Jindo applications could send and receive mircopayments making it easier for developers to build towards a machine-payable web?