Software developers appreciation post
Summary
A user expresses gratitude to open source developers, highlighting vllm's recent major releases that fixed OOM issues, allowing doubling of context window size to 240k on a 5090 with Qwen 27B.
Similar Articles
Devs - you have 64gb of VRAM - which model do you use for coding?
A developer with 64GB VRAM shares their preference for an unsloth version of Qwen 3.5 122b-a10b for coding and asks the community for their recommendations.
@leopardracer: THIS AMERICAN DEVELOPER SPENT WEEKS DEBUGGING TIMEOUT ERRORS IN OLLAMA. THEN HE LOOKED UNDER THE HOOD LM Studio is just…
A developer fixed persistent timeout errors in Ollama by using llama.cpp directly, bypassing wrappers like LM Studio and Ollama, achieving 53 tok/s on an M1 Max with 262K context.
Qwen3.6 27B more dumb in vLLM compared to llama.cpp
A user reports that the Qwen3.6-27B model performs better and more reliably with llama.cpp than with vLLM, citing tool call errors and 'lobotomized' behavior in vLLM despite extensive configuration.
Tested how OpenCode Works with SelfHosted LLMS: Qwen 3.5, 3.6, Gemma 4, Nemotron 3, GLM-4.7 Flash - v2
A developer benchmarked multiple self-hosted LLMs (Qwen 3.5/3.6, Gemma 4, Nemotron 3, GLM-4.7) with OpenCode on two coding tasks, revealing speed and quality trade-offs on RTX 4080 hardware.
Qwen3.6 27B local vs Opus 4.8, voxel engine in raw C with zero frameworks
Compares Qwen3.6 27B running locally against Opus 4.8, and highlights a voxel engine built in raw C with zero frameworks.