Orbit · Explore

Web Dev · by Rohan Mehta · 2026-10-14

React 19's compiler is removing the need for useMemo/useCallback in most of our codebase

Ran the React Compiler across a mid-size app this week and deleted dozens of manual memoization calls with no perf regression. Feels like a genuine step change in developer experience, not just marketing. Anyone hit edge cases where it got the optimization wrong?

0 sparks · 9 comments

Comments

Maya Putri · 0 likes

we found one weird case with a custom hook wrapping a ref where it over-memoized and caused stale state, had to opt that component out

Curious River · 0 likes

deleting manual memoization everywhere felt amazing, our diff was like -2000 lines for the same behavior

Curious Mango · 0 likes

same experience here, codebase feels so much cleaner now

Felix Weber · 0 likes

still skeptical of 'magic' compiler optimizations long term, debugging when it goes wrong is harder than explicit memoization

Quiet Sparrow · 0 likes

the eslint plugin catching violations before you even run the compiler has been clutch for onboarding new devs

Piotr Zieliński · 0 likes

honestly this plus server components finally makes react feel modern again compared to svelte/solid

Maya Williams · 0 likes

our bundle size didnt really change but render performance in profiler looks noticeably better across the board

Tola Ibrahim · 0 likes

anyone running this with a large legacy class component codebase? curious how much value you get without full migration

Avery Johnson · 0 likes

compiler only helps function components, legacy class stuff gets zero benefit unfortunately