The Trap of Memoizing Everything
What you'll learn: Why wrapping every component and value in memo, useMemo, and useCallback creates more problems than it solves.
The Allure of Memoization
After learning about React.memo, useMemo, and useCallback, it's tempting to wrap everything. "If memoization prevents unnecessary work, why not use it everywhere?" This logic seems sound—but it creates code that's harder to understand, harder to maintain, and often no faster.
The Hidden Costs
Memoization isn't free. Each wrapper adds:
- Memory overhead: Cached values must be stored
- Comparison overhead: React must check if dependencies changed
- Cognitive overhead: Readers must understand why something is memoized
When you memoize components that re-render quickly anyway, you're paying these costs for zero benefit. Worse, you're cluttering your code with optimization logic that distracts from actual business logic.
The Readability Problem
Compare these snippets:
// Over-memoized
const value = useMemo(() => a + b, [a, b]);
const handler = useCallback(() => console.log(value), [value]);
// Clear and simple
const value = a + b;
const handler = () => console.log(value);
The second version communicates intent instantly. The first forces readers to ask "Why is this memoized? Is there a performance issue here?"
The Right Approach
Profile first. Use React DevTools to identify actual performance problems. Memoize the specific components or values causing measurable slowness—not everything "just in case."
Think of memoization like adding salt: a pinch in the right place enhances the dish. Too much everywhere ruins it.
Key Takeaway: Blanket memoization sacrifices code clarity for imaginary performance gains. Memoize strategically based on profiler data, not as a default habit.