News for hackers. Stuff that matters.
Re:Qwen3.8-27B by NitpickLawyer on Friday August 14, 2026 @11:25AM (#49300040)
> Beats Opus 4.7 Max

I'm a huge open model fan, and have used them since forever, even have daily drivers for on-prem dev, but no. They do not beat opus on real-world usage.

Qwen models are impressively good for what they are, are "good enough" for plenty tasks, can be ran locally on decently priced hardware, and so on. They certainly have their uses, and the field in general has advanced faster than my early expectations. But to compare a 27B model to SotA behemoths from a few months ago is doing everyone a disservice, especially people who pick it up, try to use them just like API models, and leave disappointed and confused. Number goes up on a benchmark isn't it.

Re:Qwen3.8-27B by spmurrayzzz on Friday August 14, 2026 @11:34AM (#49300183)
> They do not beat opus on real-world usage

We have an internal eval that measures performance on tasks for a handful of embedded systems repos for our mmWave radios (mostly Rust, some C for microcontroller stuff). Qwen3.6-27B scores only 4% lower for pass@1, n=250 compared to Opus-4.8.

For the labeled dataset, the average PR size they're being measured against is around 1.5k SLOC.

This is very much "real-world usage" for us. The sort of change sets that come in daily/weekly and are solving non-trivial issues in the respective codebases.

As is usually the case, the most broad claims from both the labs and from the consequent pushback are talking past each other.

Re:Qwen3.8-27B by cyanydeez on Friday August 14, 2026 @12:36PM (#49301118)
Let us know when you have Qwen vs Qwen comparison stats. As long as there's not a regression, that'd be awesome.
Re:Qwen3.8-27B by spmurrayzzz on Friday August 14, 2026 @12:39PM (#49301162)
4% is within the margin of error anyways for pass@1, so I think pass@k > 1 is gonna be the better indicator of any movement (still need to calibrate the optimal k to re-test). 10 seems too tolerant even though that tends to be the next tranche I reach for.
Re:Qwen3.8-27B by croemer on Friday August 14, 2026 @12:59PM (#49301463)
Depends on where you sit on the binomial curve. At p=0.04 for n=250 4% points would not be within margin of error.
Re:Qwen3.8-27B by spmurrayzzz on Friday August 14, 2026 @01:35PM (#49301988)
Right I take your point, but that's not the comparison in this case though. These are paired results on the same 250 tasks, so whether a 4 point gap is meaningful depends on the task-level deltas, not just plugging p=0.04 into the binomial SE.
Re:Qwen3.8-27B by croemer on Friday August 14, 2026 @12:58PM (#49301443)
How much does it score though? 0% would be 4% less if Opus was at 4%. Unless you mean relative fraction not percentage points - but people usually mean percentage points in such situations.
Re:Qwen3.8-27B by tyre on Friday August 14, 2026 @01:34PM (#49301970)
0% is not 4% less than 4%, that would be 3.84%.

0% is 4 percentage points (pp) less than 4%.

Re:Qwen3.8-27B by enraged_camel on Friday August 14, 2026 @01:26PM (#49301866)
>> We have an internal eval that measures performance on tasks for a handful of embedded systems repos for our mmWave radios

Okay but the parent said real-world usage, presumably meaning coding tasks.

We have a whole bunch of complex evals that Haiku 4.5 passes. That doesn't mean it is a good model for coding.

Re:Qwen3.8-27B by spmurrayzzz on Friday August 14, 2026 @01:36PM (#49301999)
Yes, these are coding tasks in the embedded systems domain (I mentioned Rust and C).
Re:Qwen3.8-27B by graceful6800 on Friday August 14, 2026 @03:00PM (#49303165)
They literally stated in their first sentence that it was coding tasks.
Re:Qwen3.8-27B by KronisLV on Friday August 14, 2026 @11:32AM (#49300155)
> ...but no. They do not beat opus on real-world usage.

I agree, but then we just need meaningful benchmarks that clearly show that! Otherwise it's hand waving about something that should be put on paper in quantifiable terms.

Re:Qwen3.8-27B by pimeys on Friday August 14, 2026 @12:01PM (#49300608)
If you are working in a company and using language models, it is a very good idea to hold a bunch of evals you can trust and use to validate new models. Calibrate every once in a while with prod data. We have our own and the only numbers on quality and cost I trust come from this setup.
Re:Qwen3.8-27B by niek_pas on Friday August 14, 2026 @11:37AM (#49300222)
A wise man once said, "not everything that counts can be counted, and not everything that can be counted counts".
Re:Qwen3.8-27B by valvar on Friday August 14, 2026 @04:47PM (#49304389)
That’s well and good, but how are we supposed to evaluate the accuracy of random HN comments without anything resembling somewhat objective metrics? People say all manner of things, and usually it’s contradictory. What heuristic do you propose?
Re:Qwen3.8-27B by bewareofscams on Friday August 14, 2026 @11:38AM (#49300233)
Only useful benchmarks are those you (in particular) don't have access to.
Re:Qwen3.8-27B by rhdunn on Friday August 14, 2026 @12:52PM (#49301347)
The only useful benchmarks are those you've created for your specific workflow. Only then can you assess whether a given model is better or worse for what you are using it for.

There are tools like promptfoo designed for this.

Re:Qwen3.8-27B by xienze on Friday August 14, 2026 @11:41AM (#49300296)
> but then we just need meaningful benchmarks that clearly show that!

That's the rub. AI benchmarks are IMO, by and large totally unreliable. We think of them as similar to traditional benchmarks of deterministic processes where the number of variables is low. But they're anything but that. Non-deterministic processes with an astounding number of variables and fuzzy acceptance criteria.

It leads to results like these, where if you take it at face value, the only conclusion you can draw is "wow Anthropic must be stupid if Opus takes 1T parameters to do what Qwen can do in 27B."

Re:Qwen3.8-27B by mlmonkey on Friday August 14, 2026 @12:19PM (#49300861)
In the end, the only benchmark that matters is your own.
Re:Qwen3.8-27B by willcmcc on Friday August 14, 2026 @12:28PM (#49301004)
There is 0 shot you can make that claim about this model you have not used or downloaded yet
Re:Qwen3.8-27B by metadat on Friday August 14, 2026 @12:34PM (#49301086)
How can you say this when you haven't even tried it yet? Is it just hypothetical vibes?
Re:Qwen3.8-27B by altmanaltman on Friday August 14, 2026 @12:38PM (#49301153)
"Benchmark is stupid" and "model beats model on benchmark" are two different things, though. The second one is objectively true regardless of your views on the first one, right? To expect everyone to share your opinion that benchmarks are stupid is pretty weird, and just saying "no" to an objective truth is the definition of delusion.
Re:Qwen3.8-27B by kennywinker on Friday August 14, 2026 @01:56PM (#49302303)
If a benchmark is a measure of nothing useful, then model beats model is an objectively useless fact
Re:Qwen3.8-27B by altmanaltman on Friday August 14, 2026 @03:35PM (#49303585)
But that's the problem with that logic. The author subjectively claims benchmarks are stupid (a debatable opinion) and treats that as inherently true while making the second claim (hence, you shouldn't say model A beat model B).

I can say I find the law stupid, so no one should say person A beat person B in court. But I did not prove the law is stupid; I merely thought it subjectively and demanded others to follow the second part because I believe the first part is true.

Saying that "if the law is useless, court cases are useless" is objectively true and cannot be argued with. But you still need to prove why the law is useless, not why you think it is and even then if people disagree and use the law as a reference, then it's not objectively useless and court cases are not useless as well.

Re:Qwen3.8-27B by redox99 on Friday August 14, 2026 @12:57PM (#49301426)
Yep. These small models are actually worse than GPT 3.5 at some tasks (like recalling facts). You can definitely make models smarter at specific tasks (like tool calling, coding) but you can't compress the entire human knowledge into a 30GB file. It's just not enough bits.
Re:Qwen3.8-27B by ferrouswheel on Friday August 14, 2026 @01:51PM (#49302224)
But why would you use a model to store factual knowledge, that is stupid. We want intelligence, not a database.
Re:Qwen3.8-27B by tonis2 on Friday August 14, 2026 @02:39PM (#49302894)
Models cant make any decisions if they have 0 idea that the feature exist in this language or in some general fact.

For example you would tell a model hey, become an expert in this language for me, search it online, it would still need to learn it and download the data to it's context and then increasing the memory usage, there's no way around it.

Re:Qwen3.8-27B by ferrouswheel on Saturday August 15, 2026 @12:29AM (#49307644)
Implicit knowledge is different from remembering every church that exists in the state of NSW Australia
Re:Qwen3.8-27B by ycui7 on Friday August 14, 2026 @01:25PM (#49301840)
that is why we enable web search for the agent. the memory can come from the internet.

deepseek-v4-flash needs web search to return true facts.

Re:Qwen3.8-27B by redox99 on Friday August 14, 2026 @01:47PM (#49302157)
Yeah but results are worse, see https://news.ycombinator.com/item?id=49301574
Re:Qwen3.8-27B by mirekrusin on Friday August 14, 2026 @05:27PM (#49304808)
That's a good sign.

Ideal local model would not know stuff like who Britney Spears is, best to leave precious weights for something useful.

Of course the line is very blurry but I'd be perfectly happy with local model that doesn't know anything about history, geopolitics, art or even biology etc. just coding, operating systems etc.

Re:Qwen3.8-27B by Azantys on Friday August 14, 2026 @07:22PM (#49305794)
At one point there were specific -Coder release of Qwen e.g. 2.5 but they dropped that, still wondering how much better 3.6-Coder or 3.8-Coder would be when they ignore everything else
Re:Qwen3.8-27B by anon373839 on Friday August 14, 2026 @07:38PM (#49305903)
In my experience, the facts that are compressed away in small models are ones you don’t need them to memorize. They need familiarity with the essential concepts in a field, so that they will have better comprehension of material put into the context (and make better retrieval decisions). They don’t need to know very particular details which are a hallucination risk and should be derived from the context instead.