[dudeinhawaii]

I think for many/most programmers = 'speed + output' and webdev == "great coding".

Not throwing shade anyone's way. I actually do prefer Claude for webdev (even if it does cringe things like generate custom CSS on every page) -- because I hate webdev and Claude designs are always better looking.

But the meat of my code is backend and "hard" and for that Codex is always better, not even a competition. In that domain, I want accuracy and not speed.

Solution, use both as needed!

[falloutx]

> I actually do prefer Claude for webdev

Ah and let me guess all your frontends look like cookie cutter versions of this: https://openclaw.dog/

[Yiin]

Yes and I love it.

[whynotminot]

> Solution, use both as needed!

This is the way. People are unfortunately starting to divide themselves into camps on this — it’s human nature we’re tribal - but we should try to avoid turning this into a Yankees Redsox.

Both companies are producing incredible models and I’m glad they have strengths because if you use them both where appropriate it means you have more coverage for important work.

[flir]

That's the best theory I've heard. Or at least, it's the one that fits with my usage. I'm mostly-backend, and I'm mostly-GPT.

(I'm also a "small steps under guidance" user rather than a "fire and forget" user, so maybe that plays into it too).

[theLiminator]

Actually for me the killer feature isn't Claude, but is the planning mode.

It's a very nice UX for iteratively creating a spec that I can refine.

[Dma54rhs]

Codex has it as well now.