Om Next Quick Start

Lots of new stuff in Om Next. Unlike Relay and Falcor we have recovered HTTP caching <a href="https:&#x2F;&#x2F;github.com&#x2F;omcljs&#x2F;om&#x2F;wiki&#x2F;Remote-Synchronization-Tutorial" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;omcljs&#x2F;om&#x2F;wiki&#x2F;Remote-Synchronization-Tut...</a>. And due to the redesign Om Next now has a really fantastically simple automated testing story <a href="https:&#x2F;&#x2F;github.com&#x2F;omcljs&#x2F;om&#x2F;wiki&#x2F;Applying-Property-Based-Testing-to-User-Interfaces" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;omcljs&#x2F;om&#x2F;wiki&#x2F;Applying-Property-Based-Te...</a><p>Happy to take any questions.

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.<p>That all being said, David Nolan is clearly a gamer -- Om will be interesting to watch even for people who aren&#x27;t using it.

I was hoping that in om next boilerplate will be cleaned up, but seems like it&#x27;s not really different from original om. No reify is nice though.

Works great with React Devtools [0]!<p>[0] <a href="https:&#x2F;&#x2F;chrome.google.com&#x2F;webstore&#x2F;detail&#x2F;react-developer-tools&#x2F;fmkadmapgofadopljbjfkapdkoienihi?hl=en" rel="nofollow">https:&#x2F;&#x2F;chrome.google.com&#x2F;webstore&#x2F;detail&#x2F;react-developer-to...</a>

As the author of Coils, another Clojure framework (coils.cc) I am really impressed to see Om Next, and I think that Om Next will become the de facto framework for building interactive websites

What about performance? How many data queries can it handle per component, realistically? How many connections can it handle? I.e., where will this solution break down?<p>Are the transactions (issued from within the browser) performed optimistically? If so, will this not give &quot;flicker&quot; in the browser in case a transaction needs to be rolled back? Is it also possible to easily perform a transaction from the server (i.e., not optimistically)?