I think part of the reason some people feel this way about Om is that it was built as an experiment - specifically an experiment about handling immutable state in React.
I find that Om has very strong opinions about doing state the clojure way, but is a very thin wrapper around the rest of React's API - which leads to a feeling of inconsistency.
Some of the stuff David's suggested will be part of "Om next" I think will address this.
I find that Om has very strong opinions about doing state the clojure way, but is a very thin wrapper around the rest of React's API - which leads to a feeling of inconsistency.
Some of the stuff David's suggested will be part of "Om next" I think will address this.