I was looking through the CircleCI front-end application (https://github.com/circleci/frontend) and noticed that they do not use `transact!` to update the app state. All user actions are placed on a channel and processed by a single handler function. This handler function calls out to various multimethods that mutate the app state accordingly using `swap!`. Doesn’t this defeat the whole purpose of using Om? By not taking advantage of cursors, could they have accomplished the same level of component modularity by using Reagent with a single atom? Curious if Om offers any other benefits that I’m not aware of.
Thanks! -Scott -- 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.
