[gtf21]

This looks like a very appealing framework, but reminds me of the horrors of using Google Web Toolkit or Meteor. There are different concerns when writing on the client (less controlled) and the server (more controlled) - chvid mentions the security model being different, and this is very true.

The use-case which I think this does seem to solve very well is between dynamic and static rendering of web apps (especially when using react). The ability to bundle up routing and rendering and have it handled by the client if possible and the server if not is a great idea. Apart from this, I am not convinced that this framework solves any major problems, but does introduce a lot more magic (which is why I disliked meteor).

[piercey4]

I agree with you 100%. You can take this hammer and use it like a axe. But that's not the goal.

My personal setup has been to still separate my api (although still written in Rill) from all of this) which runs as an independent server. Then I have an isomorphic Rill instance communicate with that API. This way I still keep the important things separate.