> Reagent is more than just a thin veneer over React. It does quite a bit of > work, just as Om does. This is subjective, but Reagent feels more easy than > simple to me. Sometimes, that’s what you want; sometimes it’s not. But: I’ve > barely touched Reagent myself, so take that with a large grain of salt. I’d > love to hear a response from someone actually working with Reagent.
OK, I'll bite. I'm bothered by your use of the term "easy". As I'm sure you know, that has a negative connotation in our community, and your remarks seem to imply that Reagent is a toy not to be taken seriously for non-trivial apps. That is certainly not the case. To me, Reagent feels simple, as in just the right level of abstraction, whereas Om feels like incidental complexity. This is just my opinion, but I think perhaps much of the initial popularity of Om was due to the rock-star status of its creator (no disrespect intended - David Nolen IS a rock star in this community, and has made tremendous contributions to our community, and I am very grateful for that). But many people, including myself, seem to be finding the additional complexity unwarrranted in some (most) cases and switched to Reagent. They are BOTH excellent libraries, and it really comes down to which one fits your app and/or your team's mental model best. From my experience, Reagent is generally easier to work with, and you have a lot of flexibility with structuring your app state, which could be good or bad depending on what you are looking for. Om is much more prescriptive, which can be a good thing too - if you have no idea how you should structure your app, well Om might be a good choice because it does force you into doing things a certain way. One thing I did early on when trying to decide between Om and Reagent was write a small but non-trivial part of my app in both. I used Kioo for templating, so I didn't have to write the view code twice, plus having all the markup in templates let me really focus on how I was managing state in both versions. I found it very useful, and I think it just makes sense to do a small spike like this before committing to a particular library for a large project. One last thing - Dmitri Sotnikov has written some nice blog posts on Reagent, which are really helpful for getting starting. I recommend starting with this one: http://yogthos.net/#/blog/54 There is also one on how to do routing with Reagent: http://yogthos.net/#/blog/55 -- 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 clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
