[hawkice]

I use Reagent (another Clojurescript React library), and it seems this might widen the gap between the two in terms of ease-of-getting-started. Reagent is dead simple to get going with, and requires you learn basically nothing to build even moderately complicated things. Om is... somewhat notorious for having more complex abstractions built around deep thought about maintaining e.g. a single point of mutable data. This new stuff is... not something I think I could get right the first try.

That all being said, David Nolan is clearly a gamer -- Om will be interesting to watch even for people who aren't using it.

[jraines]

Reagent is very nice and by itself very easy to get started with.

That said, I think Om Next is more comparable to Re-frame (https://github.com/Day8/re-frame) as far as being more opinionated about handling data flow.

In that comparison, I don't think it involves any more complex abstractions or deep thought. In both cases, there is some of that, but both cases are also shining examples of explanatory documentation, which to me were edifying to read because they turn those abstractions into concrete implementations, with examples, and explain the deep thought in a clear manner.

[Skinney]

If you use re-frame with reagent (and you should) then the ideas aren't that difficult to grasp. Om.next is more oppinionated regarding where you're allowed to run queries (subscriptions in re-frame) and transactions (handlers in re-frame), and forces you to build a single large query from the root component (wheras re-frame allows you to run several queries from every component).

[ams6110]

Link for the curious: https://holmsand.github.io/reagent/

[amelius]

What I always worry about is not the ease-of-getting-started, but more the ease-of-scaling-modification-and-extending :)

[moomin]

The jury remains out on that one too. Om is a bit marmite. :)