[dead]
We made Grok 4.5, GPT-5.5, and Claude build the same apps
41–50 of 97 posts
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#42Why not wait one more day for GPT-5.6?
If we wait for the next models, we will never test anything because there will always be another model. Like the Ai Scotsman: > "Nay, laddie, that’s no’ the real AI Scotsman! He’s grander still! More powerful! Just wait for the next model!"
I think he’s being sarcastic
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#43> The receipts: speed and cost
I don't get why cost per reply is at all relevant here?
Why do so few who attempt comparisons actually compare dollars per task.
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#44I get the point of this demo but if instructions are clear, tech stack related resources are available, then the models do not differ as much.
I use different models all the time. And mostly lower cost ones. I do not know how people write software these days, but I have clean instructions, usually in Epics and they have Tasks.
I have been using DeepSeek V4 Flash for much of my coding in https://github.com/brainless/akar for example. Planning is mostly done by Qwen latest (in opencode) or Sonnet.
For my commercial, client work I use Claude but barely use Opus. Sonnet does most of the work. For a recent project, I went through a 35 page PRD in about 4 weeks, that includes client calls, changes, Ecpi/Task generation, a massive test suite, deployment.
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#45Earlier quoted context omitted.
This is the real unlock of the speed and value monster. I am trying to figure out how many LLM converged on a writing style that resembles a LinkedIn MBA true believer. Maybe because there was just such a sheer mass of corporate-speak drone writing out there in the wild in the training data set? But more seriously, is there a firefox extension that 'skims' the text body content of a page and puts some kind of "this w…
It's kinda logical. Most people, individually, have a somewhat unique writing style. So if there's one set of writing that's very formulaic and consistent and you build an averaging machine it's going to converge on that formulaic style because everyone else's writing style is going to be much closer to n=1.
I'd expect that most corporate speak made it past their data curation, while normal people speaking normally was probably scrutinized a bit more heavily. The PC stuff is also probably quite terrified of a lot of adjectives. For instance I just used normal as an adjective, and that can be a hyper-loaded term if somebody's obsessed with trying to interpret things in the most absurdly bad faith way imaginable. By contrast corporate speak tends to have obnoxious lingo, but lingo that can't really be spun too much. Even for one of those guys, mental gymnasticing 'snappy' into being a secret dog whistle's going to be pretty hard.
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#46> The receipts: speed and cost I don't get why cost per reply is at all relevant here? Why do so few who attempt comparisons actually compare dollars per task.
Tokens per task might be the better choice
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#47I am 99% sure the post was written by AI
Either that or a human that has started writing like an LLM, having been "trained" on LLM output itself by sufficient exposure.
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#48> The receipts: speed and cost I don't get why cost per reply is at all relevant here? Why do so few who attempt comparisons actually compare dollars per task.
Tokens per task might be the better choice
Why do I care how many tokens were used? 50,000 or 5,000,000 all I care about is the output quality, speed, and the cost.
Re: We made Grok 4.5, GPT-5.5, and Claude build the same apps
#49If you like this kind of comparison, we have an arena of 52 apps one-shotted across 21 models here: https://arena.logic.inc/
I keep it pretty up to date (tomorrow Grok 4.5 and Sonnet 5 should be pushed).