Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A week of using Codex more than Claude

allaboutcoding.ghinda.com

Post reply on HN
Print view View original

41–50 of 311 posts

Re: A week of using Codex more than Claude

#41

Post by king_crimson »

trjordan wrote: post #31
217 wrote: post #10

while everyone is somehow still stuck on and fascinated by claude, heres your quick update on the sota of coding models and harnesses mid august 2026 codex is good, both cli and desktop app, you get lots of usage on any plan. sol is good! and gets the job done, write or dictate a very long and thoughtful prompt, and leave sol xhigh or max fast working on it for an hour or so omp is an amazing harness, any feature cla…

Not mentioning Grok 4.6 here is a crime. Fast and accurate. And it can communicate, unlike the gobbledygook that comes out of Claude.

Been working a lot recently with Grok 4.6 for implementation and gpt 5.6 sol for review. Worked really good so far.

Re: A week of using Codex more than Claude

#43

Post by ibramGaunt »

217 wrote: post #10

while everyone is somehow still stuck on and fascinated by claude, heres your quick update on the sota of coding models and harnesses mid august 2026 codex is good, both cli and desktop app, you get lots of usage on any plan. sol is good! and gets the job done, write or dictate a very long and thoughtful prompt, and leave sol xhigh or max fast working on it for an hour or so omp is an amazing harness, any feature cla…

My token usage on Claude models has dropped by 83% over the last month - I'm pretty much only using it for quick one off questions or reading papers. it feels impossible for me to get Opus models to stop entering into cyclic loops, and my work is too security adjacent for Fable.

Codex has been an excellent workhorse - doesn't feel like I have to dance around the guardrails, doesn't lose _everything_ when it compacts, and doesn't litter the workspace with a million and one planning to plan files.

Re: A week of using Codex more than Claude

#44

Post by transdev12 »

beering wrote: post #2

> Changes created by Codex had fewer comments in Ruby/Ruby on Rails code. I liked that a lot, and I will soon share some experiments I ran on this. Why is fewer comments a good thing?

Claude comments look like this

//add returns the sum of x and y

//per section 2.1 of addition-implementation-plan.md sum is designed as the seam for user addition interfaces.

//previously sum added numbers, now it adds numbers

def add(x, y):

    return x + y

Re: A week of using Codex more than Claude

#45

Post by stillpointlab »

> Codex feels more like a version of Data from Star Trek

Great analogy for some reason. At fist I felt Codex Sol was a bit more cold. But now that I've worked with it for several weeks it has grown on me, even shown some personality. I appreciate that it is a bit more business-like, Fable is a bit too friendly sometimes when it ought to be focused on work. Codex can be a bit more nit-picky.

I agree with most of his other observations. I've already started to bin tasks based on which model I feel is best suited. In general, for well scoped and straight ahead tasks where banging out code is what I want I reach for Codex. For less specced tasks where I need a broader view and want the model to fill in more details I reach for Fable.

Both are great and they make a good team together.

Re: A week of using Codex more than Claude

#46

Post by piazz »

Summer 2026 meta (well, mine):

Sol is for routine work, Opus for frontend/design, and Fable for more complex / ambiguous / architecture work. Fable works extremely well to drive Sol as a subagent.

Fable is the only one you can actually trust to not look at the code, but Sol is somehow still more pleasant to work with, especially in fast mode. Opus is the enemy, and it will make you insane if you talk to it for too long.

Re: A week of using Codex more than Claude

#47

Post by WASDx »

beering wrote: post #2

> Changes created by Codex had fewer comments in Ruby/Ruby on Rails code. I liked that a lot, and I will soon share some experiments I ran on this. Why is fewer comments a good thing?

Good code is self-explanatory and don't need comments.

I can really recommend the book Clean Code, here is a summary: https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988c...

Re: A week of using Codex more than Claude

#48

Post by splap »

beering wrote: post #2

> Changes created by Codex had fewer comments in Ruby/Ruby on Rails code. I liked that a lot, and I will soon share some experiments I ran on this. Why is fewer comments a good thing?

I find claude often comments about what the code *does not* do. Relevant at the moment, but doesn't belong in the codebase.

Re: A week of using Codex more than Claude

#49

Post by hamandcheese »

skeledrew wrote: post #8
rirze wrote: post #3

Earlier quoted context omitted.

Claude is creating verbose comments with recent models and people are are tired of it

Those verbose comments provide context for why something is there way it is, so it can take those decisions in account when making changes in the future.

The story of how the code got to a certain state belongs primarily in git commit messages, not in comments. Comments should serve to aid in understanding of the code, highlight footguns or hidden dependencies, etc.

Claude very often litters code with comments about decisions that were made within a single session/pull request, its just noise.

Re: A week of using Codex more than Claude

#50

Post by netniuq »

transdev12 wrote: post #44
beering wrote: post #2

> Changes created by Codex had fewer comments in Ruby/Ruby on Rails code. I liked that a lot, and I will soon share some experiments I ran on this. Why is fewer comments a good thing?

Claude comments look like this //add returns the sum of x and y //per section 2.1 of addition-implementation-plan.md sum is designed as the seam for user addition interfaces. //previously sum added numbers, now it adds numbers def add(x, y): return x + y

just reading this comments made me despise the fact that I have to read this shit again tomorrow

It's really time to move to OpenAI...

Post reply on HN