GPT-5.5 vs Claude Opus 4.7: what 15 developers chose.
381 opinions. 15 developers named a direct preference: GPT-5.5 12–3. Approval is 69% vs 42%.
If you want code quality, choose GPT-5.5. If you want speed, choose Claude Opus 4.7. The 12–3 direct split is not a landslide; it is a difference in working style.
Choose GPT-5.5 if you…
- Want stronger code-quality sentiment and higher approval
- Care about speed and reliability
- Want more evidence from a larger comment base
Choose Claude Opus 4.7 if you…
- Put planning and architecture first
- Prefer a model that pushes back on bad ideas
- Can absorb more cost and limit complaints
Code quality for GPT-5.5. Speed for Claude Opus 4.7.
Net sentiment per topic: praise minus complaints, as a share of mentions. Positive means more praise than complaints. Hover a dot for the raw counts.
Net sentiment = praise minus complaints, as a share of each tool's mentions. The dot lanes are only for readability; position is the score.
View data table
| Topic | GPT-5.5 | Claude Opus 4.7 | Mentions |
|---|---|---|---|
| Code quality | +60 | -10 | 114 / 51 |
| Speed | +86 | +43 | 14 / 7 |
| Reliability | +6 | -53 | 32 / 34 |
| Autonomy | +20 | -53 | 15 / 17 |
| Cost & pricing | +11 | -50 | 18 / 12 |
| Usage limits | +20 | -75 | 5 / 8 |
The same decision, from both sides.
Paraphrased from comments where a developer named a preference or described a switch. Each links to the original.
Picked GPT-5.5 12 developers
Said GPT-5.5 with extra-high reasoning caught more edge cases and analyzed more deeply than Opus 4.7 and 4.8 in peer review.
Found the benchmark out of step with experience and favored GPT-5.5 for practical day-to-day coding.
I have been doing more experiments with what I have now been calling agentic iterative optimization: telling the LLM to optimize code such that it speeds up all real-world-representative benchmarks by X% without cheating or causing regressions in both tests and performance metrics (e.g. MSE for statistical algorithms or file size in the case of something such as image compression). This is done using Rust where there are more low-level levers to tweak for performance than something like Python. Opus 4.6/4.7 was consistently successful at getting 2-3x speed improvement with just one pass. It ca
Rated Codex computer use above Claude's and GPT-5.5 above Opus 4.6 and 4.7.
Picked Claude Opus 4.7 3 developers
Preferred Opus 4.7 for planning and architecture because it pushes back on bad ideas, while using GPT for pure coding.
Cited a performance benchmark where Opus 4.6 and 4.7 slightly beat GPT-5.5, matching their own experience.
Found the models hard to separate after internal tests but slightly preferred Opus 4.7's style.
The numbers.
| Metric | GPT-5.5 | Claude Opus 4.7 |
|---|---|---|
| Approval | 69% | 42% |
| Last 90 days | 67% | – |
| Opinions | 236 | 145 |
| Developers | 221 | 136 |
| First-hand opinions | 203 | 122 |
| Direct picks | 12 | 3 |
| Type | Model | Model |
| Made by | — | — |
Related matchups.
GPT-5.5 vs Claude Opus 4.8
12–8 direct picks, and a clear difference in what developers optimise for.
Claude Opus 4.6 vs Claude Opus 4.7
12–2 direct picks, and a clear difference in what developers optimise for.
GPT-5.5 vs Claude Fable 5
8–5 direct picks, and a clear difference in what developers optimise for.
How to read this comparison.
Approval is the positive share of opinions that took a side, with the rank based on the lower bound of a 90% confidence interval. Direct picks count comments where a developer explicitly preferred one tool or described switching. Small samples are noisier; check the opinion counts.
Get the monthly report
Which AI coding tools gained or lost developer approval on Hacker News, and why people switched. One email a month.