Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

modelscope.cn

Post reply on HN
Print view View original

171–178 of 178 posts

Re: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

#171

Post by SwellJoe »

embedding-shape wrote: post #169
jcsycombinator wrote: post #165

Earlier quoted context omitted.

If you can't get Qwen 3.8 27b to work well that's a skill issue. You just suck at using ai

Which exact quantization you use of that particular model? I've just spent two days testing it qualitatively (after the quantitative results were kind of bad, but promising), the official BF16 weights, and it keeps fucking up very basic things, like doing "rm -rf sessions/$id" without really checking or making sure $id is defined, so it ends up deleting more. I'd love it if local LLMs actually could replace remote on…

To be fair to Qwen, we've all been there.

Re: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

#173

Post by embedding-shape »

SwellJoe wrote: post #171
embedding-shape wrote: post #169

Earlier quoted context omitted.

Which exact quantization you use of that particular model? I've just spent two days testing it qualitatively (after the quantitative results were kind of bad, but promising), the official BF16 weights, and it keeps fucking up very basic things, like doing "rm -rf sessions/$id" without really checking or making sure $id is defined, so it ends up deleting more. I'd love it if local LLMs actually could replace remote on…

To be fair to Qwen, we've all been there.

Maybe I got lucky (as I know others have had this issue), or it recovered by itself, but never had this happen with GPT models for as long as I've used codex, and I run it with "--sandbox danger-full-access --dangerously-bypass-approvals-and-sandbox" 100% of the times.

Re: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

#174

Post by julianlam »

hgoel wrote: post #147
rdsubhas wrote: post #137

Earlier quoted context omitted.

How do you folks code at 40-50 tps? With an extremely lightweight harness (pi) and just 8k system and tools context, and ~40tps on qwen 3.8 27B 4-bit on low thinking mode, it still takes me nearly 30-45 mins for a basic coding session... Does it work? yeah... But I'd pick a subscription anyday...

Do you find subscriptions to be meaningfully faster? I didn't really feel too much of a speed difference compared to Opus.

When you hear stories like "Opus 5 thought for 20 minutes and then denied my request" it really puts wind in this sails of Local LMs

Re: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

#175

Post by bicepjai »

rdsubhas wrote: post #137
pwython wrote: post #11

I was already rolling around the idea of a 128GB M5 Max MBP. Now this! A 4-bit MLX quant with 128k window should fit perfectly, in the 50-70 tok/s range.

How do you folks code at 40-50 tps? With an extremely lightweight harness (pi) and just 8k system and tools context, and ~40tps on qwen 3.8 27B 4-bit on low thinking mode, it still takes me nearly 30-45 mins for a basic coding session... Does it work? yeah... But I'd pick a subscription anyday...

There is a finite amount of time left for these companies to become next Facebook/Google, hoarding our interaction and privacy will be a point of contention pretty soon. At that moment, Qwen will be the knight in shining armor.

Re: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

#176

Post by yencabulator »

vorticalbox wrote: post #104
WiSaGaN wrote: post #85

Earlier quoted context omitted.

You probably meant Qwen3.8-35B-A3B. But judging from some of the words from their team, it seems unlikely unfortunately.

They normally release a 35b dense and an 27b moe (4B active per token) For context 35B on my m4 runs at 10 tokens a second, 27B moe runs 50-60 tokens a second.

27B dense or 35B-A3B MoE. You might be confusing it with Gemma 4 that has a 26B-A4B variant.

Re: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

#177

Post by [deleted] »

SwellJoe wrote: post #40

Finally, a reason to own a 128GB Strix Halo or GB10 device. Or a reason to consider the new Mac Studio. I have a Strix Halo and dual 32GB GPUs in my desktop, and the latter is pretty much always better for running local models because it's quite a bit faster due to higher memory bandwidth. There simply haven't been any models that are better than Qwen 27B or Gemma 31B, which run comfortably in 64GB with big context.…

[deleted]

Re: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)

#178

Post by SwellJoe »

embedding-shape wrote: post #173
SwellJoe wrote: post #171

Earlier quoted context omitted.

To be fair to Qwen, we've all been there.

Maybe I got lucky (as I know others have had this issue), or it recovered by itself, but never had this happen with GPT models for as long as I've used codex, and I run it with "--sandbox danger-full-access --dangerously-bypass-approvals-and-sandbox" 100% of the times.

No, I mean, every human who spends enough time working with computers eventually makes a dumb blunder, very often this specific one (using `rm -rf` in a way that has further reaching effects than intended). But, I do want to use models that don't make those kinds of mistakes, which is why I happily pay for a bunch of subscriptions for the best models.
Post reply on HN