> The first company's frontend would render a given screen 12+ times for some state changes

Might just be me, but it feels like a good framework/library would put in a lot of work to avoid or at least alert about these kinds of issues so they can’t stay very long without being fixed.

I’ve seen the same in React (even infinite render loops which couldn’t be ignored and had to be fixed) and to a lesser degree with the likes of Vue as well.

I’m not sure what’s missing but having a tool that is easy to use in the wrong way doesn’t inspire confidence.