Why Developers Keep Choosing Claude over Every Other AI
51–60 of 85 posts
Re: Why Developers Keep Choosing Claude over Every Other AI
#52I've been using ChatGPT (Thinking). I like how it has learned how I do stuff, and keeps that in mind. Yesterday, I asked it to design an API, and it referenced a file I had sent in, for a different server, days earlier, in order to figure out what to do. I'm not using it in the same way that many folks do. Maybe if I get to that point, I'll prefer Claude, but for my workflow, ChatGPT has been ideal. I guess the best…
Worth noting that Claude also has a memory feature and uses it intelligently like this, sometimes more thoughtfully than cgpt does (fewer “out of left field” associations, smoother integration).
Re: Why Developers Keep Choosing Claude over Every Other AI
#53Re: Why Developers Keep Choosing Claude over Every Other AI
#54Was it ever confirmed that Anthropic did paid astroturfing? Or is this organic?
Re: Why Developers Keep Choosing Claude over Every Other AI
#55Re: Why Developers Keep Choosing Claude over Every Other AI
#56When I am using an LLM for JS, I can't really tell the difference between the two. For C#, I think GPT might produce slightly better quality code, but Claude produces code that seems more modern. I also feel like Claude makes slightly more minor mistakes like forgetting to negate a boolean conditional check.
With Swift, I have found both models to be surprisingly awful. I am not sure if it is because of some of the more recent changes with Swift versions greater than 6.0, but both seem to produce wild results for me.
[1] I do not use Codex CLI nor Claude Code nor any IDE plug-ins. I just type questions into the web app and rarely copy/paste anything back and forth.
Re: Why Developers Keep Choosing Claude over Every Other AI
#57Claude the model or Claude (Code) the tool? I'm not sure what to think about an article that doesn't make it clear which one they are talking about...
Re: Why Developers Keep Choosing Claude over Every Other AI
#58Could it be tooling like Claude Code? I just used Claude Code with qwen3.5:35b running locally to track down two obscure bugs in new Common Lisp code I wrote yesterday.
I use Claude Code as an orchestrator and have the agents use different models: product-designer ollama-cloud / qwen3.5:cloud pm ollama-cloud / glm-5:cloud test-writer claude-code / Sonnet 4.6 backend-builder claude-code / Opus 4.6 frontend-builder claude-code / Opus 4.6 code-reviewer codex-cli / gpt-5.1-codex-mini git-committer ollama-cloud / minimax-m2.5:cloud I use ollama pro $20/month and OpenAI $20/month. I have…
Re: Why Developers Keep Choosing Claude over Every Other AI
#59I don't think vibe coders know the difference, but often when I ask AI to add a feature to a large code base, I already know how I'd do it myself, and the answer that Claude comes up with is more often the one I would have done. Codex and Gemini have burned me too many times, and I keep going back to Claude. I trust it's judgement. Anthropic models have always been a step above OpenAI and Google, even 2 years ago it…
Re: Why Developers Keep Choosing Claude over Every Other AI
#60Model aside, the harness of Claude Code is just a much better experience. Agent teams, liberal use of tasks and small other ergonomics make it a better dev tool for me.
I've heard a lot of people prefer OpenCode to Claude Code, myself included. Having tried both, I find myself having a much better time in OpenCode. Have you tried it? I'll admit it lacks on the agent teams side but I tend to use AI sparingly compared to others on my team.
1. No clipboard image paste. In Claude Code I constantly paste screenshots – a broken layout, an error dialog, a hand-drawn schema – and just say “fix this.” OpenCode on Windows Terminal can’t do that without hacky workarounds (save to file, drag-and-drop, helper scripts). I honestly don’t understand how people iterate on UI without this. 2. Ctrl+C kills the process instead of copying. And you can’t resume with --continue either, so an accidental Ctrl+C means losing your session context. Yes, I know about Ctrl+Ins/Shift+Ins, but muscle memory is muscle memory. I also frequently need to select a specific line from the output and say “this part is wrong, do it differently” – that workflow becomes painful. 3. No step-by-step approval for individual edits. Claude Code’s manual edit mode lets me review and approve each change before it’s applied. When I need tight control over implementation details, I can catch issues early and redirect on the spot. OpenCode doesn’t have an equivalent.
All three might sound minor in isolation, but together they define my daily workflow. OpenCode is impressive for how fast it’s moving, but for my Windows-based workflow it’s just not there yet.