[madeofpalk]

This looks like a really interesting model, less hacky than the current approach of 'lets take client-side react-router and somehow make it work on the server' approach.

What isn't answered here however is how it transfers this 'config' and the rest of the state and make it work in the browser. Does rill come with its own client-side router (that works nicely with React?) How does it serialise the state and send it down for the client resume?

Ultimately, the reason 'universal javascript' is hard is because everything's 'modular' so you can get more controller over each component and customise exactly how it works. While rill might be 90% for 90% of use cases, I can see something like this falling down once you start to build anything non-trivial.

[piercey4]

What I use to handle state transfer from the server to the client is @rill/session along side @rill/loader. Check them out and feel free to ask me any questions (here or in the gitter!)