I love local models, and I run 3.8 Flash Next on a dedicated machine. Alone with a number of image and video generation models. But if I'm doing REAL work, that isnt tinkering for fun on a side project, im using claude, because Qwen3.8 just cant handle large context project well without going off into left field.
Im SUPER jazzed for qwen4 with 1mil token context native support. I HOPE it a step up from 3.8 flash next. Ill be playing with all the qwen4 models the moment I can, but I dont see how someone working on large code bases doing REAL enterprise grade work is seriously using any local models in any capacity that comes remotely close to Opus 5.5+Claude
Sorry, but this is either dilettante talk or an unhinged exaggeration - Qwen, DS, GLM and MM are perfectly fine for REAL work, unless you are an overly ambitious vibe coder, but then no model can save you. The Cl hand-holding may feel like something but it won't lead to the completion of real REAL work.
I suspect that's because they're working on projects that are several orders of magnitude more complex and demanding than a "todo app".
The same way people have opinions on things like for example wines without actually being able to discern them in a blind test.
We humans want to think we can have strong, well founded opinions even when we cannot.
Their point may also be (re: wine), that some devs have been conditioned to think a certain token vendor (vineyard) is of superb quality, while if given a blind test (tasting) of the agents on a real world task, they would not notice the difference.
For those of us who use open weights, the difference has narrowed dramatically this year. I've personally been mostly eyes-free developing an NES harness with mostly flash models, bringing in Kimi from time to time, and stepped in a couple times to reframe the approach or architecture. For those of us who (when we) stay in the loop, the difference is near-zero because the tasks we give them are more bite sized.
The difference I have observed is most closely tied to the complexity or context requirements. While I work in a multi-million LoC codebase without any issue for open weights or flash models, my NES project is only 20k lines. The challenging part is the core loop (which needs to blend the emulator FPS with the agent loop) and game state observation (needs to detect byte changes in emulator RAM). The ROM decoding itself has not been so bad, I have actually been quite impressed with the little open weight models on this front. After it extracted the maps, then pulled out even more details, it has written an A* implementation that requires moving between different modes of transportation. (Final Fantasy 1)
Yes, this was the core of my point.
GLM flash catches Claude errors and bad assumptions, all LLMs make mistakes