FYI: Qwen3.8 27B is still a Qwen3.5 architecture model (Qwen3_5ForConditionalGeneration in config.json); Qwen3.8-Flash-Next – a different model, despite the similar name – is the Qwen4 preview (Qwen4ExpForConditionalGeneration).
I believe what they’re saying is that since we didn’t get a MoE around the 35B-A3B size for the Qwen3.8 generation of releases that this model might be able to fill that niche – i.e. a better model than Qwen3.6 35B-A3B while still being less compute intensive to run than Qwen3.8 27B.
Yeah, exactly, and sorry to everyone if I was unclear. I’m not holding out hope for a Qwen 4 35b-a3b either, so it’s good to see a model that comes close to 3.8 27b in benchmarks and I hope they stay competitive with Qwen 4 27b as well.
FYI: Qwen3.8 27B is still a Qwen3.5 architecture model (
Qwen3_5ForConditionalGenerationin config.json); Qwen3.8-Flash-Next – a different model, despite the similar name – is the Qwen4 preview (Qwen4ExpForConditionalGeneration).I believe what they’re saying is that since we didn’t get a MoE around the 35B-A3B size for the Qwen3.8 generation of releases that this model might be able to fill that niche – i.e. a better model than Qwen3.6 35B-A3B while still being less compute intensive to run than Qwen3.8 27B.
AHH cool, I didn’t thought both 3.8 models were on 4 architecture, I’ll edit my previous comment 👍
Yeah, exactly, and sorry to everyone if I was unclear. I’m not holding out hope for a Qwen 4 35b-a3b either, so it’s good to see a model that comes close to 3.8 27b in benchmarks and I hope they stay competitive with Qwen 4 27b as well.