Frameworks just dont give af cause framework authors are out here busy trying to monopolize ALL THE STARS (dev mindshare, basically). Just look at Hooks and Re

Frameworks just dont give af cause framework authors are out here busy trying to monopolize ALL THE STARS (dev mindshare, basically). Just look at Hooks and React. How many posts have we seen where people demonstrate the authors could've done something different, without buggering with what the meaning of a call site in a React component is, or even accomodated hooks in the Class API, but React devs can get away with this cause they don't need to prove coherent technical benefits, they just need to make it look like "the next big thing". Numerous frameworks solve the problem of cross-cutting state concerns targeted at distinct sub-trees in the your UI (see mobx/freactal/etc). The componentDidMount/componentDidUpdate simplification is nice, but could've been accomodated in the Class API. Other reasons like "readability" or some shit, I honestly don't give af cause these are subjective statements that aren't at all neccesarily related to a solution's quality per project