A MacBook Air running Qwen locally took 63 hours to produce a "flyable but ugly" flight simulator; the same task handed to Google AI Studio produced a complete version in 20 minutes.
What concerns us isn't how rough the aircraft is, but what the gap between 63 hours and 20 minutes reveals about the real state of local large models.
What This Is
The original post came from Reddit's r/LocalLLaMA community. The author used LM Studio to load a 3-bit quantized version of Qwen 27B (quantization compresses model size; 3-bit is extreme compression — heavy information loss, but still runnable), paired with a 57k context window (the amount of input the model can "see" at once). The first prompt — "write a beautiful flight simulator in a single-page HTML" — ran for 47.8 hours and output a page that said "press any key to start" but did nothing when keys were pressed. The second prompt — "I pressed the keys but nothing happened" — ran for another 15 hours and produced a working version that "sort of moves forward, has no plane model, and has bugs."
The comparison: Google AI Studio output a complete version with a plane model and smooth terrain in 20 minutes. Qwen's online Studio completed the task in 2 hours, but with flickering terrain glitches.
Industry View
The local LLM community is treating this experiment as a milestone: a consumer laptop "barely" completed an agent-style task (letting AI autonomously pursue multi-step goals, not just single-turn Q&A). Under 3-bit quantization, information degrades sharply and capability loss should be severe in theory — but the task finished, and the community reads that as proof of open-source resilience.
The criticism is just as sharp: 63 hours versus 20 minutes is a chasm, not a gap. The hidden costs of local deployment are being underestimated — the electricity drain from a fully loaded machine and the opportunity cost far exceed cloud API fees. Acceptable as a one-time curiosity; completely impractical as a productivity tool. Technical voices also point out that a 3-bit quantized model producing flight-simulator code likely means flight simulators were common training data. Switch to a more obscure task and the failure rate climbs sharply.
Our sober read: local large models suit "no rush, tolerate rough output" scenarios — offline learning, privacy experiments, low-frequency tasks. Real work output still depends on the cloud.
Impact on Regular People
For enterprise IT: local LLM deployment remains in the "technical validation" phase. Unless you're in finance, healthcare, or government — sectors with strict data-egress rules — the ROI isn't there yet. Worth watching, not worth rushing a project for.
For individual professionals: stick with cloud tools like ChatGPT, Wenxin Yiyan, Tongyi, and similar for daily work. Running models locally is a "pseudo-need" for most white-collar workers — unless you're an AI engineer or a hardcore tinkerer.
For the consumer market: next year, PC makers will heavily promote "AI PC" and "local large model" as selling points. When you see the marketing, ask one question: how long does an actual task take? Can a 3-bit quantized version handle real work? Don't fall for the pitch.