4 ms·
I think it's more than the median developer, and I think part of it may be due to React being a victim of its own success in some ways. The scope of requirement
by CSSer 4y ago
I think it's more than the median developer, and I think part of it may be due to React being a victim of its own success in some ways. The scope of requirements for many kinds of common hooks has expanded dramatically. Yesterday I found a problem in a hook that is part of a library downloaded 1M+ times a week.
- penumbral 4y agoIMO it's more like anyone who doesn't spend over 50% of their time thinking about React re-renders whenever they're in a React component. The level of effort to properly use hooks is insane, so them being touted as a "less boilerplate!" way of writing "more functional" (literally the opposite in practice) code is egregious.
- Rapzid 4y agoYep, here is the React Router team getting it wrong(among other things): https://github.com/remix-run/react-router/issues/7634 https://github.com/remix-run/react-router/issues/7634
- CSSer 4y agoI meant for this to be included in the scope of my comment but I was short on time. You stated it better, and you’re completely right. The problem I was alluding to was related to a hook deciding when to rerender based on dependency lists. It was setup such that some people may expect it to rerender in a certain case and others may not, and it wasn’t an uncommon or excessively complicated use-case. React can’t win here because they have a hard stance on when to value performance (avoiding re-renders) vs. convenience (ease of abstraction usage).
- CSSer 4y agobecause they don't have a hard stance* important typo there.