DevConsensus
Models / Qwen 3.6
Model · HN opinions Nov 2025 – Nov 2026

Qwen 3.6: what developers actually say

We read every Hacker News comment from Nov 2025 – Nov 2026 that gave a real opinion on Qwen 3.6. 79 of the 94 opinions come from people who say they use it themselves.

76%approval, all opinions
71%approval, last 90 days
#11of 45 models ranked
80different developers

Developers give Qwen 3.6 76% approval across 94 opinions from 80 authors, with 79 firsthand reports. Approval over the last 90 days is 71%, below the overall figure. Monthly samples are uneven: 82% in April, 72% in June on 37 opinions, and 88% in September; the two October opinions scored 25%, too small a sample to read as a trend. Code quality (25 positive, 6 negative), local privacy (21 positive, 2 negative), and speed (13 positive, 1 negative) drive the positive case; reliability is split at 4 and 4.

Pick it if

  • Want local inference for privacy-sensitive work
  • Value fast answers on a Mac
  • Need a low-cost local model for simple tasks

Look elsewhere if

  • Need reliable agentic coding on large repos
  • Plan to run quantized local builds for agent tasks
  • Need a local model for moderately complex coding

Strengths and weaknesses

Each row counts opinions that mentioned the topic. Bars to the right of the line are praise, bars to the left are complaints.

PraiseComplaints
Code quality
6
25
Privacy & local use
2
21
Speed
1
13
Reliability
4
4
Cost & pricing
4
Autonomy
1
2

How opinion has moved

050100Apr '26May '26Jun '26Jul '26Aug '26Sep '26
Monthly approval (line) and number of opinions (bars). Months with fewer than 3 opinions are left out.

What developers say

Praise

Uses local Qwen 3.6 35B for speed on a 128 GB MacBook.HN comment · Sep 23, 2026
Finds local Qwen 3.6 fast on a MacBook.HN comment · Sep 22, 2026
Runs a local Qwen 3.6 MoE on an M3 Max at about 90 tokens/sec to generate tested code.HN comment · Sep 14, 2026
Used Qwen 3.6 for research and orchestration, praising its speed and capability for the project.HN comment · Aug 30, 2026
Says Qwen 3.6 35B-A3B answered an Xlib question concisely and correctly without needing web search.HN comment · Aug 18, 2026
Says Qwen 3.6 handles their WordPress and SQL tests very well.HN comment · Aug 12, 2026
Uses Qwen 3.6 for everything because swapping models on a single-model machine costs too much time.HN comment · Aug 12, 2026
Uses Qwen 3.6 27B for personal projects and finds it works pretty great.HN comment · Aug 11, 2026

Complaints

Says Qwen 3.6 misdiagnosed bugs, gave wrong fixes, and wrote very slow code on the same codebase.HN comment · Oct 26, 2026
Says quantized Qwen 3.6 is not good at agentic tasks and often invents details about documents.HN comment · Aug 7, 2026
Ran Qwen 3.6 directly on a code review in a 30M+ line repo and exhausted its context window.HN comment · Aug 3, 2026
Says Qwen 3.6 35B MoE stalls on bigger projects and struggles to hold large scopes locally.HN comment · Jun 29, 2026
Says local quantized Qwen 3.6 handles most agent tasks well but falls short for coding.HN comment · Jun 26, 2026
Says the local Qwen 3.6 35B output quality is too weak for moderately complex coding tasks.HN comment · Jun 15, 2026
Says Qwen 3.6 gave no good results on their local agentic tasks.HN comment · Jun 14, 2026
Says Qwen3.6 35B and dense 27B are too slow and weak for agentic coding, and get stuck without a nudge.HN comment · May 13, 2026

Summaries are paraphrased. Each links to the original comment.

Qwen 3.6 compared

FAQ

Is Qwen 3.6 worth it?

Developers give it 76% approval, and 79 of 94 opinions are firsthand. It suits local, cost-sensitive work with strong privacy and speed scores. Reliability is even at 4 positive and 4 negative, so test it on your own workload.

Is Qwen 3.6 better than Gemma 4?

The preference data is mixed. Three developers preferred Qwen 3.6 over Gemma 4, while six preferred Gemma 4. Qwen 3.6 has strong local privacy and speed scores, so the better choice depends on your task.

Is Qwen 3.6 good for coding?

Code quality is its strongest aspect at 25 positive and 6 negative opinions. Developers report correct, concise answers and tested code generation. Others cite misdiagnosed bugs, slow code, context exhaustion on a 30M+ line repo, and weak quantized local results.