On Wed, Jan 22, 2014 at 7:18 PM, David Nolen <[email protected]> wrote:
> Fair enough. I'm still in the "local state is poison" camp though. >> Hard to get at, and against the grain of the value that Om provides. >> Being able to hold the complete state in your hand, rather than >> scattered across implementation details, is awesome. >> > > In the Om model people can choose how they divide up their state. If you > want to save everything in application state, fine. But many applications > will not want to do this. That said, I think it's useful to be able to > force a component to write its local state to some more durable location > and this is what I want to explore. > Alternatively, it's also useful to be force a component to write all of its state into component local state. This would open the door for JavaScript React components to easily use ClojureScript Om components. David -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
