Live data from Hacker News

Developers are choosing older AI models

augmentcode.com

51–60 of 179 posts

Re: Developers are choosing older AI models

#51
post #47

Earlier quoted context omitted.

That would be the browser fingerprinting in action. I often get a lot of requests to use widevine on ddg's browser on android (which informs one about it) for I suspect similar reasons.

Interesting, I'm on Brave and have never had a site request bluetooth access before, so much so that I'd never even granted Brave bluetooth access, hence why it popped up as a system notification this time around.

Doesn't Brave disable WebBluetooth by default via a flag?

Re: Developers are choosing older AI models

#52

GPT5 is HELLISHLY slow. That's all there is to it. It loves doing a whole bunch of reasoning steps and prolaim how mucf of a very good job it did clearing up its own todo steps and all that mumbo jumbo, but at the end of the day, I only asked it a small piece of information about nginx try_files that even GPT3 could answer instantly. Maybe before you make reasoning models that go on funny little sidequests wher they…

This. Speed determines whether I (like to) use a piece of software.

Imagine waiting for a minute until Google spits out the first 10 results.

My prediction: All AI models of the future will give an immediate result, with more and more innovation in mechanisms and UX to drill down further on request.

Edit: After reading my reply I realize that this is also true for interactions with other people. I like interacting with people who give me a 1 sentence response to my question, and only start elaborating and going on tangents and down rabbit holes upon request.

Re: Developers are choosing older AI models

#53
I use both Codex and Claude, mostly cuz it's cheaper to jump between them than to buy a Max sub for my use-case. My subjective experience is that Codex is better with larger or weird, speghetti-ish codebases, or codebases with more abstract concepts, while Claude is good for more direct uses. I haven't spent significant time fine-tuning the tools for my codebases.

Once, I set up a proxy that allowed Claude and Codex to "pair program" and collaborate, and it was cool to watch them talk to each other, delegate tasks, and handle different bits and pieces until the task was done.

Re: Developers are choosing older AI models

#54
post #48

I usually switch models depending on the situation, for simpler stuff, I lean toward 4o since it’s faster to get answers. But when things get more complex, I prefer GPT-5, talking with it often gives me fresh ideas and new perspectives.

You might be the first technical user spotted out in the wild who actually prefers 4o for anything.

Re: Developers are choosing older AI models

#55
I think this is one of the many indicators that even though these models get “version upgrades” it’s closer to switching to a different brain that may or may not understand or process things the way you like. Without a clear jump in performance, people test new models and move back to ones they know work if the new ones aren’t better or are actually worse.

Re: Developers are choosing older AI models

#56
I wish we could pin down not only the model but also the way the UI works as well.

Last week Claude seemed to have a shift in the way it works. The way it summarises and outputs its results is different. For me it's gotten worse. Slower, worse results, more confusing narrowing down what actually changed etc etc.

Long story short, I wish I was able to checkpoint the entire system and just revert to how it was previously. I feel like it had gotten to a stage where I felt pretty satisfied, and whatever got changed ... I just want it reverted!

Re: Developers are choosing older AI models

#58
> Each model appears to emphasize a different balance between reasoning and execution. Rather than seeking one “best” system, developers are assembling model alloys—ensembles that select the cognitive style best suited to a task.

This (as well as the table above it) matches my experience. Sonnet 4.0 answers SO-type questions very fast and mostly accurately (if not on a niche topic), Sonnet 4.5 is a little bit more clever but can err on the side of complexity for complexity's sake, and can have a hard time getting out of a hole it dug for itself.

ChatGPT 5 is excellent at finding sources on the web; Gemini simply makes stuff up and continues to do so even when told to verify; ChatGPT provides link that work and are generally relevant.

Re: Developers are choosing older AI models

#59
post #52

GPT5 is HELLISHLY slow. That's all there is to it. It loves doing a whole bunch of reasoning steps and prolaim how mucf of a very good job it did clearing up its own todo steps and all that mumbo jumbo, but at the end of the day, I only asked it a small piece of information about nginx try_files that even GPT3 could answer instantly. Maybe before you make reasoning models that go on funny little sidequests wher they…

This. Speed determines whether I (like to) use a piece of software. Imagine waiting for a minute until Google spits out the first 10 results. My prediction: All AI models of the future will give an immediate result, with more and more innovation in mechanisms and UX to drill down further on request. Edit: After reading my reply I realize that this is also true for interactions with other people. I like interacting wi…

> Imagine waiting for a minute until Google spits out the first 10 results.

what if the instantaneous responses make you waste 10 min realizing they were not what you searched for?

Post reply on HN