> React’s logical model of recreating the UI on change of state is incredibly difficult to do right at scale. What's much more difficult at scale is doing this

> React’s logical model of recreating the UI on change of state is incredibly difficult to do right at scale. What's much more difficult at scale is doing this without React. In the old days when building a complex front-end web app, your app would slowly devolve into complex web of event handlers changing the DOM, and you'd eventually arrive at the conclusion that you'd eventually arrive at the conclusion that centralizing state and triggering UI updates based on those changes was the only sane thing to do. And then you'd end up either: 1) re-rendering the whole DOM on ALL state changes -- which came without its own set of problems of which performance was just one, or 2) manually hooking up callbacks to change pieces of the DOM as the relevant pieces of state changed -- which was only slightly less of a nightmare to maintain then the event handler spaghetti you were coming from. Also another dev your team would always just hook up and event another event handler to change the DOM somewhere, and ignore your state entirely. React actually made this both much more performant and much easier to maintain. If you aren't building a complex web app with a lot interconnected interactions and state changes, you don't have to use React. If you are, I encourage you to build it with jQuery, and look forward to your follow up blogpost.