Rather than repeat my response to the solid criticism here I'll link to the reddit conversation where I talk about some of the solutions and pending solutions <a href="https://www.reddit.com/r/Clojure/comments/2jq0cu/om_no_trouble_in_paradise_with_clojurescript_and/" rel="nofollow">https://www.reddit.com/r/Clojure/comments/2jq0cu/om_no_troub...</a>
I agree. I've had a few troubles with Om, and while dnolen and the community have been super helpful on IRC and lists, there are some basic things that I personally felt trapped by.<p>- The inability to cleanly have om components co-exist with a static template, rather than having to render the entire thing using sablono or om/goog is one. The rationale is that multiple roots aren't good for you, but the alternative is to render your entire template within clojurescript code which can be a pain if you're working with someone who thinks in html/css.<p>- The API for IResolve is currently in super early alpha, and while there are some examples [1], one of the the recommended solutions [2] is to use NativeStore or Derive, which seems overkill for simpler use cases such as mine.<p>(It isn't my intention to be <i>overtly</i> critical of a great library - I like it a lot. I've used it to some extent and faced a bunch of issues, which I hope will get resolved over time as the APIs and design become more stable.)<p>[1] <a href="https://github.com/swannodette/om/blob/master/examples/two_lists/src/core.cljs" rel="nofollow">https://github.com/swannodette/om/blob/master/examples/two_l...</a>
[2] <a href="https://groups.google.com/forum/#!topic/clojurescript/WCz57-k8leY" rel="nofollow">https://groups.google.com/forum/#!topic/clojurescript/WCz57-...</a>