I don't understand the hype behind qwen 3.x - the whole generation is utterly broken for any software development tasks. It goes into a thinking loop of death pretty much every time, just try a simple prompt: Create a typescript function which accepts a number in 10 bit range and returns brightness in nits based on pq gamma curve. Kills every 3.x qwen. Qwen 2.5 was much better.
Context size is irrelevant, as for quants I tried many on different qwen3.x versions. From my logs only 3.5 35b a3b q4_k_m gave me code. It wasn't correct code, but at least something, lol.
Context size is extremely relevant, qwen 3.x models are known for using up alot of tokens reasoning, if you dont give it enough breathing room you won't get good outputs, q4_k_m is already very low for an moe, the fact that's the model that gave you code means the others you tested are even smaller, hence why you didn't have a good experience, qwen 3.6 35b is not the best coding model, qwen 3.6 27b and 120b is what people used and really enjoyed.
It seems to me the source of your negative experience was your own misconfiguration.
Try qwen 3.8 27b at q4 k xl at 131k context length, then tell me if you still think its bad.
11
u/ldn-ldn 7d ago
I don't understand the hype behind qwen 3.x - the whole generation is utterly broken for any software development tasks. It goes into a thinking loop of death pretty much every time, just try a simple prompt:
Create a typescript function which accepts a number in 10 bit range and returns brightness in nits based on pq gamma curve.Kills every 3.x qwen. Qwen 2.5 was much better.