@dominicm I'd like to second what @lilactown said, there might be situations where Reagent might be slower than React, but in general use, you are unlikely to run into them. Also, you can concoct situations where Reagent is actually faster. Etc.

https://www.freecodecamp.org/news/a-real-world-comparison-of-front-end-frameworks-with-benchmarks-2018-update-e5760fb4a962/

@doglooksgood my guess is that you are generating a giant ball of DOM.

This may help https://github.com/Day8/re-frame/blob/master/docs/Performance-Problems.md#2--on-big-structures

Looks like migrating Reagent away from deprecated componentWillMount lifecycle method wasn't too complicated: https://github.com/reagent-project/reagent/pull/443

Re, yesterdays performance discussion. In certain cases using Sablono or Hicada with Reagent can improve the performance. Reagent has to convert all hiccup structures into React elements runtime (as we don't use any macros) but these libs can compile most Hiccup into React element calls in macro compliation time. (https://github.com/rauhs/hicada). Though the Reagent implementation caches the conversion so usually it should be quite okay.

UIx is saying it's interpreter (i.e. Hiccup to React elements on runtime) is 2x faster than Reagent so I guess there is room to optimize Reagent implementation.

@mikethompson great resource! looks like reagent is fast when compare to vanilla react. I'll take a look at the re-frame performance doc.

And well, @roman01la already asked me I'd be interested merging some performance improvements he found when creating UIx. And obviously I said I'd be very interested in them 🙂