[rubicon33]

> The whole point of react is to avoid the stateful nightmare created by the latter approach.

I found this ironic, as I have never in my life had more struggles with state, than when working with react native. Seriously, the amount of times something didn't update, or was updating way too many times, is countless. It's so easy to shoot yourself in the foot. Imperative native programing, almost never have this issue.

[chmod775]

You could try angular then, though at some point you're going to run into a similar problem: your zone not becoming stable (mostly a problem when writing tests) because of some external dependency using a setTimeout or setInterval*. But at least it's generally pretty fast at updating and works without shoehorning you into one way of managing state.

Overall I prefer React because I prefer simple composable libraries over frameworks and Angular reminds me too much of programming in Java with its long application boot times and its folders full of ListUpdateCheckerConditionFactoryBeanUnitTest.java's.

*To be fair, in an equivalent React app, at that point you would have had to write a whole lot of shouldComponentUpdate to not tank performance.