Colin Hunt
Aug 28, 2017 · 1 min read

Your entire argument seems to boil down to ‘if you are passing new objects to a PureComponent, it will always rerender, so PureComponents are harmful.’ Well this is a very narrow judge of PureComponent’s utility, imo.

I believe if one is following the practice of caching objects that are sent as props instead of creating new objects each time if their content hasn’t changed, or if your component only uses primitives as props, then PureComponent is valuable as it saves you from the boilerplate of checking each prop individually.

Thus, PureComponent is quite a useful tool provided you understand its limitations — as with all tools.

)

    Colin Hunt

    Written by