This week on Reddit's LocalLLaMA (a developer community focused on local deployment of open-source LLMs), a user publicly posted requesting Google release a new version of Gemma—specifically calling for a 220B-scale QAT (Quantization-Aware Training, a compression technique that lets models run efficiently on lower-spec hardware) version; a 120B version would be an acceptable fallback.
The post was short, but behind it we see the competitive landscape of open-source LLMs. Meta's Llama, Mistral, Alibaba's Qwen, and DeepSeek have noticeably denser iteration cadences. Google's Gemma has already been viewed by the developer community as the one that has "fallen behind."
What this is
The 220B-scale version this user publicly requested reflects a demand for MoE (Mixture of Experts, an architecture that splits one large model into multiple "expert" sub-models activated on demand—the current mainstream efficiency route). Technical details like QAT and n-gram don't require deep explanation for general readers, but MoE has become standard in open-source LLMs—mainstream players have largely switched. Whether Google's Gemma follows suit is exactly the core demand behind this post.
Industry view
The open-source camp generally believes that Google, with its top-tier AI R&D resources (DeepMind, research labs), is moving slowly on open-weight models as a matter of strategic choice—not lack of capability.
But commercial analysts offer a different take: Google's core revenue still depends on cloud services and closed-source APIs (Gemini), and over-investing in open source would undercut its own products. This "betting on both sides but committing fully to neither" posture is making Google appear passive on both fronts.
A risk worth flagging: if the new Gemma version doesn't adopt MoE architecture, developers will likely collectively shift to Qwen or DeepSeek, further weakening Google's voice in the open-source ecosystem.
Impact on regular people
For enterprise IT: more companies are considering building private AI systems with open-source models to avoid data leakage and API price hike risks. If the Gemma series keeps pace, it becomes an additional option for budget-sensitive mid-sized enterprises.
For individual careers: employees won't encounter model version numbers in their daily work for now, but rapid progress in open-source models means that within the next 1–2 years, the cost of deploying AI inside enterprises may drop further—relevant to the tools you use every day.
For consumer markets: consumers won't feel the difference in the short term. But if open-source models catch up with closed-source ones, AI application pricing and feature options will change, which may ultimately transmit to the prices of phone assistants and office software.