Although even this one needs to be taken with a grain of salt. Fable/Opus still act very differently to Astra and Argon imo. But maybe it's just because I am used to these. I wouldn't clearly put them above each other though, although I still prefer anthropics models, but that could be simply out of comfort.
The only exception on the chart is DeepSeek - it scores exceptionally low there, which doesn't exactly track my experience. It usually does what you tell it to, and it's not exceptionally intelligent, but I do find it quite good at what it does (the bulk of code, scripting, etc). I know a lot of folks like it too ... curious if I'm just not exploring the simpler models enough?
Q: In C23, attributes are allowed in an unbraced (forward) union declaration only in the form “union [[...]] Tag;”. What single character must immediately follow the identifier in that declaration for the attributes to be permitted?
A: ;
[1] https://huggingface.co/datasets/ArtificialAnalysis/AA-Omnisc...Edit: The other programming ones look fine, bad luck I saw this one first I guess.
I keep having problems with them not doing the thing I ask, (and also failing to call tools correctly in pi. I think they've very much trained to the harness, which is frustrating.).
The harness I've built for it is pretty straight forward: split binary into individual functions, give the agent a bunch of small tools to diff output with underlying binary, make them wrote clean c until there's a certified match.
Rin a final oracle to make sure the agent isn't cheating.
- Qwen 3.8 27b on my 5090, barely acceptable, thinks too long, sometimes freaks out.
- deepseek flash variants, work horse. Runinfra provides around 300 tok/s. Great for tearing through moderately complex functions
- glm and kimi k.3, expensive, slow, ultimately not that much better than deepseek flash for this task. Better at doing long context research into old compiler productions
- sol 6.1, best bang for buck. Creative enough to methodically work through more complex spellings
But I found there were around 1% of functions that these models simply cannot solve. Opus and Astra take them handily.
I'm still still in the process of looking through the solution traces, but from watching the missing sauce seems to be creative reasoning.
Sol 6.1 will just happily grind on permutations of a base shape spelling that M2C outputs, where opus and Astra immediately realize that they need to unwind assumptions taken for granted (and sometimes in the process endure a worst match).
I'm hoping to be able to capture that creativity step and distill it into the harness tools.
I think looking at some more niche benchmarks helps, I created one and it does show Kimi K3.1 Pro as the most intelligent of all open-weight models, though it is still significantly below Opus 5/5.5[1]
If you're in a stable codebase with lots of best practices, patterns, controls (linters, analyzers, etc.), examples already established, then any model will do ~the same plus/minus since there's not much novelty.
If you're building ground up, entirely novel, no reference, I think results will vary with lower capability models.
For me, I do a mix, leaving implementation to Haiku/Luna/DeepSeek and research/feedback/critique to Opus/Sol/Astra/Fable
I would love a benchmark suite that better reflects real-world coding performance, as having Muse Wonder in the top three makes no sense to me.
I took the output and original specs and handed them to Claude today and the level of insight and concise detail in it's criticism and problem solving was fantastic. Dropped the others immediately