React Compiler
Ranked 2 of 5 JavaScript compilers by recommenders
Automatically adds memoization to React code, replacing manual useMemo, useCallback and memo, with people reporting render gains in production. Critics note skepticism about the automatic approach and mixed results.
Automatically adds memoization to React code, replacing manual useMemo, useCallback and memo, with people reporting render gains in production. Critics note skepticism about the automatic approach and mixed results.
16 people gave an opinion
- recommend it
- 10
- criticize it
- 6
- approval share
- 63%
Recommended in 7 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 10 people recommend itNeeds 10 or more, met.
- 1.6 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 7 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Automatically replaces manual memoization boilerplate
“It's very easy to configure and can automatically deal with many cases of useMemo / useCallback / memo to reduce boilerplate in code”
Comment from 26 May 2026 in “Does Anybody Actually Like React?” “all useMemo and useCallback can be removed and you get the same runtime performance and then some”
Comment from 10 Jun 2026 in “Port React Compiler to Rust” “with React Compiler it's actually pretty good at automatically adding those”
Comment from 31 Dec 2025 in “Win32 is the stable Linux ABI” - Comment from 16 Feb 2026 in “JavaScript-heavy approaches are not compatible with long-term performance goals”
Reduces unnecessary renders and boosts performance
“React compiler is awesome for minimizing unnecessary renders”
Comment from 3 Nov 2025 in “Why Nextcloud feels slow to use” “the render performance gain has been massive”
Comment from 10 Jun 2026 in “Port React Compiler to Rust” Works well in production codebases
“Performance has been fine overall, and we haven't ran into any major bugs attributable to it in that time.”
Comment from 10 Jun 2026 in “Port React Compiler to Rust” “Already being used in production at large code bases.”
Comment from 22 Mar 2026 in “JavaScript Is Enough” “It really does work very well in practice.”
Comment from 10 Jun 2026 in “Port React Compiler to Rust” Matches or beats manual optimization
“all useMemo and useCallback can be removed and you get the same runtime performance and then some”
Comment from 10 Jun 2026 in “Port React Compiler to Rust” “the Compiler now does this for you and better than you ever could manually”
Comment from 16 Feb 2026 in “JavaScript-heavy approaches are not compatible with long-term performance goals”
What people warn about
Each mark is one comment
Skepticism about automatic memoization approach
“I been very skeptical of the automatic memoization features”
Comment from 10 Jun 2026 in “Port React Compiler to Rust” “It's the definition of overengineering IMHO.”
Comment from 5 Sep 2026 in “The Rust React Compiler is now native in Vite” “react compiler muddies the water a bit”
Comment from 31 Jul 2026 in “Making Referential Stability a Type”
Other JavaScript compilers people recommend
The four most recommended other JavaScript compilers, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Oxc | 14 | 6 | 70% | 9 | — | Approved |
| React CompilerThis page | 10 | 6 | 63% | 7 | — | — |
| SWC | 8 | 1 | 89% | 6 | — | — |
| Google Closure Compiler | 6 | 2 | 75% | 5 | — | — |
| Babel | 5 | 14 | 26% | 4 | — | — |
What people said
All 17 comments that mention it, newest first. Each links to the original comment.
“It's the definition of overengineering IMHO.”
“a binary for compiling your react code (totally optional btw, it's a performance optimisation)”
“react compiler muddies the water a bit”
“It really does work very well in practice.”
“it's not compatible with mobx and we didn't notice any perf gains on an existing codebase”
“I been very skeptical of the automatic memoization features”
“the render performance gain has been massive”
“ages ago when it was extremely slow”
“all useMemo and useCallback can be removed and you get the same runtime performance and then some”
“Performance has been fine overall, and we haven't ran into any major bugs attributable to it in that time.”
“the react compiler solves/will solve it”
“It's very easy to configure and can automatically deal with many cases of useMemo / useCallback / memo to reduce boilerplate in code”
“It's also not a problem with the react compiler.”
“Already being used in production at large code bases.”
“the Compiler now does this for you and better than you ever could manually”
“with React Compiler it's actually pretty good at automatically adding those”
“React compiler is awesome for minimizing unnecessary renders”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.