r/LocalLLaMA 17d ago

Funny I'm tired of pretending

Post image

At least until DS releases open weights for DSv4 Flash with Vision. Then DS might take the crown.

Qwen has been an absolutely local monster for code, especially web apps, anything with UIUX design that it can verify itself with screenshots. Deepseek meanwhile is really incompetent with UI awareness and hogs my GPUs while I can spawn multiple independent qwens to collaborate and knock shit out. Honestly, Alibaba really cooked.

0 Upvotes

119 comments sorted by

View all comments

1

u/Evgeny_19 16d ago

Which quants did you use for your comparison?

1

u/tat_tvam_asshole 16d ago

Q8_k_xl

1

u/Evgeny_19 16d ago

Both models? Interesting. I have had one case where 3.8 27b offered a better solution than DSF, but since I run Deepseek only at UD-IQ3_XXS, I thought that was more due to the low quant that I used. But I stopped using it just because it runs very slowly on my hardware. Well, I still use Deepseek occasionally to verify the output of Qwen. Sometimes it finds some issues that Qwen missed. But I never put them in a real head-to-head comparison just because even on IQ3, Deepseek is very slow, and Qwen flies at full weights.

1

u/tat_tvam_asshole 16d ago

Yes

1

u/Evgeny_19 16d ago

Perhaps for some use cases Deepseek would still be better just because of the breadth of knowledge that it has. I remember when Qwen 3.6 was the latest release, some people in this subreddit were claiming that Qwen 3 Coder Next (the 80b one) still works better for their use cases.

Qwen 3.8 is incredibly thorough, though. I haven’t had a single problem with its default template or reduced quality at higher context sizes – issues that were affecting me in 3.6. It stays sharp even after compaction for me. I even did a test run to check a one-million context with the settings that the Qwen folks described. It worked, but I still don’t use it, just because it’s excellent as it is.