title: Is React moving away from React.memo in favor of useMemo?
body: <p>Both <code>React.memo</code> and the <code>useMemo</code> hook allow performance optimizations by reducing recalculation and rerendering.  However, they work definitely in that React.memo is used to wrap a functional component and the <code>useMemo</code> hook can be used on almost any function, even pure calculations.  More importantly, <code>useMemo</code> is typically called from a parent to a child component, while <code>React.memo</code> is typically called on the declaration of the child itself.  </p>
  
  <p>While both have different advantages, one advantage of <code>React.memo</code> is that it doesn't have to be called from each parent to child relationship.  However, with the release of hooks, it seems apparent that React development wants to move towards functional components that use hooks to deal with state, side-effect events, and other effects.  While I don't think that the React development team would have the courage or disregard of their user base to remove <code>React.memo</code> any time in the next 2 years, it makes me wonder if they want end users to stop using React.memo for stylistic reasons.  Just as they have kind of passive aggressively moved away from class components in favor of functional components with hooks.  </p>
  
  <p>When using functional components with hooks, is the react framework moving away from <code>React.memo</code>?
  Would it be better to get used to using the hook version if one wants to keep up with React best practices in the future?</p>