Qwen3.8-Flash-Next
21–30 of 246 posts
Re: Qwen3.8-Flash-Next
#22Didn't expect it to beat 3.8 27B so cleanly. Opus 4.6 Max self-hosted at 30 tok/s on a 5k Macbook in Aug 2026. The LLM timelines are crazy.
I don't like these comparisons. Sure it is impressive, but it does not have a world knowledge of larger models. It has most of theirs intelligence.
Self-learning/improving would be even better but that's still a long way to go.
Re: Qwen3.8-Flash-Next
#23Re: Qwen3.8-Flash-Next
#24Re: Qwen3.8-Flash-Next
#25Re: Qwen3.8-Flash-Next
#26Adding to my homelab stack, hopefully it doesn't overthink like the little model. Actually, hoping it thinks a bit less. Wait actually I'm really praying it reasons a bit more directly. But wait, I'm really sure that it must be a bit better.
Re: Qwen3.8-Flash-Next
#27Didn't expect it to beat 3.8 27B so cleanly. Opus 4.6 Max self-hosted at 30 tok/s on a 5k Macbook in Aug 2026. The LLM timelines are crazy.
I don't like these comparisons. Sure it is impressive, but it does not have a world knowledge of larger models. It has most of theirs intelligence.
Re: Qwen3.8-Flash-Next
#28Didn't expect it to beat 3.8 27B so cleanly. Opus 4.6 Max self-hosted at 30 tok/s on a 5k Macbook in Aug 2026. The LLM timelines are crazy.
>Opus 4.6 Max self-hosted at 30 tok/s on a 5k Macbook in Aug 2026. The LLM timelines are crazy. How much memory does this translate to and what quantization (if any) were applied?
Re: Qwen3.8-Flash-Next
#29Re: Qwen3.8-Flash-Next
#30It's in Unsloth Desktop already. Looks like it's 73GB, so 128GB Mac or Strix Halo etc will work. Exciting!
Original error: llama.cpp does not support this GGUF's model architecture ('qwen4exp')
Edit : Saw the pull request, should arrive soon enough https://github.com/ggml-org/llama.cpp/pull/27742