You’re never telling React “do this”, instead it’s always “change this state” and then hope that it does what you expect it to do, but instead it re-renders 10 components for nonobvious reasons. Sure useMemo can help with this, but, eh, I just wish it worked the first way.
And every React-adjacent project either ends up abandoned or subsumed into the beast.
After having used Ember for several years I find it very sad they didn't develop a "mobile" offering, the dev experience is fastly superior (especially as it relates to state handling).
Hooks are a bit of a cancer, they leak absolutely everywhere on top of making it quite difficult to reason about re-renders.
because you didn't learn how react works and thought just knowing javascript was enough, it's very obvious and the devtools literally how you why and where you're getting extra re-renders from; but i guess whining is easier
This is essentially how DOM manipulation works, which is JS' main use case.
You’re never telling React “do this”, instead it’s always “change this state” and then hope that it does what you expect it to do, but instead it re-renders 10 components for nonobvious reasons. Sure useMemo can help with this, but, eh, I just wish it worked the first way.
And every React-adjacent project either ends up abandoned or subsumed into the beast.
After having used Ember for several years I find it very sad they didn't develop a "mobile" offering, the dev experience is fastly superior (especially as it relates to state handling).
Hooks are a bit of a cancer, they leak absolutely everywhere on top of making it quite difficult to reason about re-renders.
because you didn't learn how react works and thought just knowing javascript was enough, it's very obvious and the devtools literally how you why and where you're getting extra re-renders from; but i guess whining is easier