While the default strategy should be to not use React.memo() unless there is a good reason to use it cc @eps1lon, looking at the codebase, there is a quick win on the problem. In 99% of the cases, anytime a React element is accepted as a prop, React.memo() is a waste of CPU cycles (unless this babel plugin kicks in, which is not frequent).
Components we can make faster be removing memo:
While the default strategy should be to not use
React.memo()unless there is a good reason to use it cc @eps1lon, looking at the codebase, there is a quick win on the problem. In 99% of the cases, anytime a React element is accepted as a prop,React.memo()is a waste of CPU cycles (unless this babel plugin kicks in, which is not frequent).Components we can make faster be removing memo: