Anecdotally, my initial experience is that Reagent's state model is very attractive on a number of levels. The effects I've seen appear to be multiplied for large+complex apps and when migrating from preexisting codebases.
There are a couple of rough spots (as there are with all wrappers currently, and with React itself) - but they're notably of the superficial & correctable-in-time variety (IMO). I wouldn't normally advocate so strongly for something (certainly not repeatedly), but I feel inclined to here since I don't personally believe it's accurate to characterise the choices made by Reagent as in any way wrong or inferior. They're offering up a different set of tradeoffs that some might find beneficial. Indeed, I think it'd be premature to make any strong statements at this point since so much of our development model has recently been thrown up in the air with the advent of tool combinations like Cljs + core.async + React, and the fantastic new patterns they enable. It's just way too early to be critical of new ideas at this point. Anyway, Dan's a relatively new member of our community and I'd be sad if he felt discouraged from pursuing his ideas. I'd encourage anyone following these discussions to check out the relevant examples and decide what makes sense for your own requirements and taste. Tl;dr - let's try things, let's share the best of them, and let's build great stuff. Kumbaya and all that. Okay, I'll shut up now. Peace :-) -- 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.
