go fix
Tied for most recommended of 3 code transformation tools
Built into Go, it rewrites code using type-aware rules, letting library authors move users off deprecated functions. Critics warn it can break program semantics.
Built into Go, it rewrites code using type-aware rules, letting library authors move users off deprecated functions. Critics warn it can break program semantics.
9 people gave an opinion
- recommend it
- 7
- criticize it
- 2
- approval share
- 78%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 7 people recommend itNeeds 10 or more, not met.
- 3.5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not 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
Built into Go, no plugins needed
“callable from the command line (which means it can integrate with CI/CD or AI tools) and like I mentioned, the fact this is built into Go itself”
Comment from 18 Feb 2026 in “Using go fix to modernize Go code” “the stdlib toolchain does a lot that other ecosystems need third-party plugins for”
Comment from 17 Feb 2026 in “Using go fix to modernize Go code” Good tooling makes Go pleasant
“Its tooling like this that really makes golang an excellent language to work with”
Comment from 17 Feb 2026 in “Using go fix to modernize Go code” “This tool is way cooler, post-redesign.”
Comment from 17 Feb 2026 in “Using go fix to modernize Go code”
What people warn about
Each mark is one comment
Risk of changing program semantics
“Because it is hard to know whether or not the handle function is called in a deferred call.”
Comment from 15 Mar 2026 in “//go:fix inline and the source-level inliner” “illustrating go1.26.1 go fix source inline transformation breaking program semantics”
Comment from 15 Mar 2026 in “//go:fix inline and the source-level inliner”
Other code transformation tools people recommend
The two most recommended other code transformation tools, 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 |
|---|---|---|---|---|---|---|
| go fixThis page | 7 | 2 | 78% | 2 | — | — |
| OpenRewrite | 7 | 1 | 88% | 3 | — | — |
| Coccinelle | 7 | 0 | 100% | 3 | — | — |
What people said
All 10 comments that mention it, newest first. Each links to the original comment.
“such a nice thing for big projects”
“Because it is hard to know whether or not the handle function is called in a deferred call.”
“illustrating go1.26.1 go fix source inline transformation breaking program semantics”
“That ends up being a really powerful primitive for library authors to get users off of deprecated functions”
“What’s new, however, is the framework that allows home-grown add ons, which doesn’t have to do everything from scratch.”
“callable from the command line (which means it can integrate with CI/CD or AI tools) and like I mentioned, the fact this is built into Go itself”
“the stdlib toolchain does a lot that other ecosystems need third-party plugins for”
“Having an AST-aware rewriter that understands Go's type system is a massive upgrade over regex hacks.”
“This tool is way cooler, post-redesign.”
“Its tooling like this that really makes golang an excellent language to work with”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.