When should you NOT use React memo?

by

You should always use React.memo LITERALLY, as comparing the tree returned by the Component is always more expensive than comparing a pair of props properties

So don’t listen to anyone and wrap ALL functional components in React.memo. React.memo was originally intended to be built into the core of functional components, but it is not used by default due to the loss of backward compatibility. (Since it compares the object superficially, and you MAYBE are using the nested properties of the sub-object in the component) =)

That’s it, this is the ONLY REASON why React doesn’t use memo Automatically. =)

In fact, they could make version 17.0.0, which would BREAK backward compatibility, and make React.memo the default, and make some kind of function to cancel this behavior, for example React.deepProps =)

Stop listening to theorists, guys =) The rule is simple:

If your component uses DEEP COMPARING PROPS then don’t use memo, otherwise ALWAYS use it, comparing TWO OBJECTS is ALWAYS CHEAPER than calling React.createElement() and comparing two trees, creating FiberNodes, and so on.

Theorists talk about what they themselves do not know, they have not analyzed the react code, they do not understand FRP and they do not understand what they’re advising =)

P.S. if your component is using children prop, React.memo will not work, because children prop always makes a new array. But It is better not to bother about this, and even such components should ALSO be wrapped in React.memo, since the computing resources are negligible.

More Related Contents:

  1. The useState set method is not reflecting a change immediately
  2. ReactJS Two components communicating
  3. How to maintain state after a page refresh in React.js?
  4. Simple Component is not rendering: React js
  5. Console.log() after setState() doesn’t return the updated state
  6. Adding new data to firebase users
  7. Where should ajax request be made in Flux app?
  8. How to load image files with webpack file-loader
  9. Understanding React-Redux and mapStateToProps()
  10. React.js: Identifying different inputs with one onChange handler
  11. javascript change background color on click [closed]
  12. setState() inside of componentDidUpdate()
  13. Why do I have to .bind(this) for methods defined in React component class, but not in regular ES6 class
  14. Support for the experimental syntax ‘jsx’ isn’t currently enabled
  15. How to update the Context value in a Provider from the Consumer?
  16. Jquery in React is not defined
  17. Next.js context provider wrapping App component with page specific layout component giving undefined data
  18. What is Virtual DOM?
  19. How to manually invoke Link in React-router?
  20. reactjs and masonry layout – undefined
  21. How to download fetch response in react as file
  22. Scroll into view in react
  23. stop dragging after a limit has reached
  24. Equivalent to componentDidUpdate using React hooks
  25. reactjs event listener beforeunload added but not removed
  26. React – Dynamically Import Components
  27. React Error: “SharedArrayBuffer is not defined” in Firefox
  28. passing data from child to parent component – react – via callback function
  29. FastAPI is not returning cookies to React frontend
  30. How to set iframe content of a react component

Leave a Comment