Google Closure Compiler
Ranked 4 of 5 JavaScript compilers by recommenders
Praised for aggressive code elimination and variable renaming that few JavaScript tools match. Critics say it can break code and is being dropped from build pipelines.
Praised for aggressive code elimination and variable renaming that few JavaScript tools match. Critics say it can break code and is being dropped from build pipelines.
8 people gave an opinion
- recommend it
- 6
- criticize it
- 2
- approval share
- 75%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 6 people recommend itNeeds 10 or more, not met.
- 3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 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
Advanced optimization and renaming
“It does a level of code elimination and variable renaming at a level that no other JavaScript tool even approaches. Excellent software.”
Comment from 8 May 2026 in “ClojureScript Gets Async/Await” “the compiler itself AFAIK remains best in class and has commits on GitHub as of 15 hours ago”
Comment from 8 Apr 2026 in “JSIR: A High-Level IR for JavaScript” “probably still the most advanced JS optimized”
Comment from 10 Feb 2026 in “Show HN: Elysia JIT "Compiler", why it's one of the fastest JavaScript framework”
What people warn about
Each mark is one comment
Seen as dead or a liability
“It has become a liability in the build process and people are getting rid of it.”
Comment from 8 Apr 2026 in “JSIR: A High-Level IR for JavaScript” “the half dead "Google Closure Compiler" as an example”
Comment from 8 Apr 2026 in “JSIR: A High-Level IR for JavaScript” “get rid of the elephant in the room”
Comment from 8 May 2026 in “ClojureScript Gets Async/Await”
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 Compiler | 10 | 6 | 63% | 7 | — | — |
| SWC | 8 | 1 | 89% | 6 | — | — |
| Google Closure CompilerThis page | 6 | 2 | 75% | 5 | — | — |
| Babel | 5 | 14 | 26% | 4 | — | — |
What people said
All 9 comments that mention it, newest first. Each links to the original comment.
“which works autonomously with the javascript assets”
“It does a level of code elimination and variable renaming at a level that no other JavaScript tool even approaches. Excellent software.”
“get rid of the elephant in the room”
“It has become a liability in the build process and people are getting rid of it.”
“the compiler itself AFAIK remains best in class and has commits on GitHub as of 15 hours ago”
“the half dead "Google Closure Compiler" as an example”
“probably still the most advanced JS optimized”
“by borrowing a function from a not invoked Array broke the compiled code”
“the precision and completeness is not nearly what can be expressed in TypeScript”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.