Joined 8 years ago
{} !== {}
and that it uses reference equality as a proxy for value equality.
This is why the absolute simplest thing to do is to just memoize all the things (see https://attardi.org/why-we-memo-all-the-things/ for a deeper dive into this approach).
I know that the conventional wisdom (e.g. https://kentcdodds.com/blog/usememo-and-usecallback) is not to do that, but it's worth noting that Kent doesn't actually bring receipts for his claims, and also the discussion is typically limited to toy examples, not huge applications that have the potential for huge cascading renders when anything changes. In my own profiling of real world applications I have found that memoizing everything is not actually a performance regression. And then also consider the React Compiler, which of course does the same, at an even more fine-grained level than any human could be bothered to consistently do by hand.
That way I can use the "control" key on the opposite side of the alpha key, the same way one is meant to do with the shift key when touch typing.
There will be open-source AR projects to block those, too, one day
[0] https://github.com/amilajack/eslint-plugin-compat
[1] https://github.com/ismay/stylelint-no-unsupported-browser-fe...
