Matt, if you keep all your state in Reagent atoms, that’s perfectly fine, you’ll probably get no benefits from moving to Rum.
Rum idea is not to lock you down to a single storage model. Sometimes your dataflow is trickier that just atoms, e.g. you need components to react to DataScript events, core.async channels, ajax/websocket/webworker callbacks. In that case Rum provides well-defined API and set of basic building blocks to write components you need to. Conceptually Rum is on the same level of abstraction as Reagent or Om, but it offers additional promise: lower-level details are well-defined and open for extensions. Nikita. -- 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.
