The way you can avoid this: - design "UI struct" for what you want to display - Have React fire off events when doing actions - Those actions get piped into

The way you can avoid this: - design "UI struct" for what you want to display - Have React fire off events when doing actions - Those actions get piped into your UI-less solution - Your UI-less solution updates the "UI struct" - React updates the parts of the tree that was using part of your struct if you design this struct in the right way, you can have the updates be _very_ targetted (like, React doing basically no extra work). But your UI struct needs to be really carefully set up so you're not firing things off all over the place. I think it's still an easier problem than keeping your DOM in sync entirely, but it's unfortunately very easy to accidentally over-render still.