🚨 React developers… stop useMemo and useCallback ❌❌❌ Yes. The hooks we’ve been obsessing over for years. Gone? 😳🤯 😳🤯 😳🤯 😳🤯 For the longest time, React performance meant doing this: • Wrapping functions in useCallback 🔁 • Adding useMemo everywhere 🧠 • Using React.memo to stop re-renders 🛑 And let’s be honest… we were just guessing if it actually improved performance 😅😅😅😅😅 Welcome React Compiler (React Forget), the compiler automatically memoizes your code 🤯💡 So this means: ❌ Less useMemo clutter 🚫 ❌ Less useCallback confusion 🚫 ❌ Less performance guesswork 🤔 Frontend development is evolving fast… ⚡🚀🔥 #reactjs #javascript #webdevelopment #frontend #reactcompiler #nextjs #graphql
If you are using react compiler. You can create a whole project without using useMemo and useCallback. But it requirers to make your components pure. And there are some edge cases where you can use them. You can use these only when actually needed.
Partially true. React Compiler can reduce the need for useMemo and useCallback, but it's still early and not widely used in production. Understanding React rendering and performance patterns will still matter.
I think this take is misleading. The React Compiler is meant to reduce unnecessary manual memoization, not eliminate it. useMemo and useCallback still have important use cases - for example passing references to memoized children, caching expensive computations, or controlling effect dependencies. The compiler will handle many common cases, but not all of them. Also, saying that 'we were just guessing' isn't really accurate for most developers... React DevTools and profiling tools have existed for years, so these optimizations could always be measured. The real takeaway should be "stop overusing hooks" rather than "stop using them".