>redrawing a string doesn't need to go through 50 chained method calls to update application state
a) If you use memoization properly, and don't put all your state at the tree root, it doesn't.
b) In my experience, devs dramatically overestimate how useful such a hand-optimized fast path is, because in a real application, users expect the UI to always be consistent. It's not just about responding to a string change but also potentially the reason you're displaying a string in the first place.
And FWIW, Live is actually a lot leaner than React.
a) If you use memoization properly, and don't put all your state at the tree root, it doesn't.
b) In my experience, devs dramatically overestimate how useful such a hand-optimized fast path is, because in a real application, users expect the UI to always be consistent. It's not just about responding to a string change but also potentially the reason you're displaying a string in the first place.
And FWIW, Live is actually a lot leaner than React.