Recent submissions

Comment · 2 months ago
Yep.. for 'general purpose' use I found qwen3.8:27b to be disappointing due to overthinking. It's brutal especially considering how slow it is compared to MoE variants. It often overthinks to the magnitude of ~10x the tokens vs a ~4x faster gemma4:26b-a3b.

As a result, qwen3.8 will churn over a prompt often for 5-10 minutes while gemma4 regularly finishes the same prompt in under 20 seconds, while giving a consistent and accurate response in my favorite test case. Qwen3.8, despite churning like that, often misses with an inaccurate answer.

Obviously, 'YMMV' depending on your use case... just sharing my two cents.

Comment · 2 months ago
It's a bit deceptive to state inference speeds without mentioning the additional things you're doing to achieve them
Comment · 2 months ago
I don't know what black magic you're up to but I see more like 30-35t/s on a 16" M5 Max using 3.8:27b Q4, regardless of whether it's mlx or gguf.

qwen3.5:122b-a10b is significantly faster at around 60-65.

Comment · 2 months ago
Now? Sure seems like it's been that way for well over a decade.
Comment · 2 months ago
Yep.. it's pretty obnoxious for real-world use with the default 'xhigh' thinking. Ridiculous amount of "Wait, actually.." which might help for complex coding tasks but makes it unbearable for general purpose use.
Comment · 2 months ago
Given that it apparently defaults to 'xhigh', this is probably the answer.

Granted, it's still much lower tokens/s than you'll get out of many MoE models.

Edit: Even set to medium or low there's still a lot of second guessing, less consistency, lower 'acceptable response' rate, and slower/more token churn vs gemma4:26b-a3b. I think gemma4 is just a better 'general purpose' model.

Comment · 2 months ago
Yeah, that's probably the answer given that it apparently defaults to 'xhigh'.
Comment · 2 months ago
One thing a lot of people don't seem to factor when hyping Qwen is how much models like this tend to 'overthink' with seemingly endless 'second guessing'. 3.8 seems no different from what I've tried thus far.

As capable as it is, it's hard to justify using it when a competing model (e.g. Gemma4:26b-a3b) can consistently achieve the same or similar response with only 1/10th as many 'thinking' tokens, achieve much higher tokens/second, and take a small fraction of the time. I suppose 'YMMV' depending on your use case.

Also, I haven't used it enough yet to see if it's prone to infinite looping, but its predecessors sure were.

Comment · 2 months ago
I'm hoping too that they'll put out some MoE variants.

Qwen3.5:122b:a10b can run about twice as fast as this 27b dense model.

Edit: Like its predecessors, 3.8 seems really inclined to overthinking, and on a 27b dense model that's kind of painful. I think I'm going to stick with gemma4:26b-a3b as my go-to because it runs about 4x as fast and tends to only need a fraction of the tokens in its 'thinking' stage to get the same or similar answer.

Comment · 2 months ago
I just got this one a few days ago so it's kinda weird I've seen it mentioned or posted about multiple times since. Guerrilla marketing?

Anyway, it's definitely better than having nothing, and tests resistance as well. I tossed a couple low value/duplicate/high resistance cables because I've got too many just lying around causing clutter. Also helped 'confirm' my good (e.g. TB4+) cables that weren't labeled clearly are indeed good cables - granted, this is only as dependable as the marker chip the manufacturer added.

Comment · 3 months ago
They're definitely doing it based on IPs. I just hopped to a different VPN endpoint and it works for me again (same browser). For now.
Comment · 3 months ago
Doesn't work for me. Seems like this login gate for old.reddit is being progressively rolled out.
Comment · 3 months ago
The difference in noise pollution comes from power density & power generation, if they're doing so on site. The power demand (and resulting waste heat) absolutely eclipses that of data centers of olde.

If they're not generating power on site & creating noise/consuming local natural gas resources, they're guzzling grid power and almost certainly contributing to electrical rate increases that affect residential customers disproportionately.

Comment · 3 months ago
There's more to it than that. They're not just obnoxious to exist in the vicinity of, they also drive up local energy prices.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton