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.
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.).
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 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]
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
I really want to love this model, particularly since it's good to have an open weight model on my team so to speak, but I think I might be holding it wrong.
What are you using it for?
On an overall speed/cost/quality comparison, it seems unmatched in my experience these days.
For tasks like crawling and real time log analysis etc., the costs really add up at scale.