I think it's a matter of not having control over it. i.e. setState(...) doesn't just set the state, it triggers a re-render. Worse in angular, obj.value = 5 triggers a re-render.
For React, again, this is entirely avoided when you stay away from using state, props, setState, etc.
You can totally take control and clearly define your programming step by just using ReactDOM.render.