Performance issues are caused by much more than just should-update equality checks. There is a performance hit to re-rendering components due to updating the virtual DOM (which is a no-op in the case of pure components) and any logic required to calculate a re-render. If your render method takes 5 seconds to run, a PureComponent’s shouldComponentUpdate is signficantly faster than that same component’s render, and passing the same function reference will shave 5 seconds off its re-render time.

Senior front end engineer / charlesstover.com

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store