
Qwen (Alibaba) - review
Rating: 6.8/10.
Qwen is Alibaba's family of large language models, whose latest generation is called Qwen3. It's an interesting project because it combines two things that rarely go together in the market: genuinely strong benchmark results and open weights you can download and run yourself. For me, the most important thing is that Qwen isn't a second-tier open-source model here-in math, code, and agentic tasks, it's nipping at the heels of the commercial top tier. Add broad multilingual support and cheap API, and it becomes one of the most sensible choices when you're counting costs. My thesis is simple: if you set aside the fact that a Chinese corporation is behind the project, you get one of the best quality-to-price ratios on the market. The whole catch is that you can't set that fact aside in every use case.
Strengths
- Open weights aren't a marketing ornament, but a real advantage. You can download the model, run it on your own infrastructure, and nobody looks at your prompts. For companies that can't send data to external APIs, this is often the only path to a sensible LLM without signing in blood under someone else's terms.
- Qwen's benchmark results are strong, and not just in one narrow category. The model handles math, code, and tasks requiring step-by-step reasoning well, and successive generations clearly boost results. This isn't a model that only looks good in a table-in real work with code or logic, it actually delivers.
- Multilingual support is one of the pillars here, not an add-on. Qwen handles many languages sensibly, which matters if you work with content outside the Anglosphere bubble. Not every open model covers languages other than English this broadly, and here it's taken seriously.
- Agentic capabilities are designed for real applications. The model handles tool calling, multi-step task planning, and working in an agent loop well, not just single responses. If you're building something that needs to reach for functions and APIs independently, Qwen is a serious candidate here.
- Cost is an argument that's hard to beat. Cheap API on one hand, and on the other the ability to self-host open weights, meaning zero cost per token if you have your own hardware. At large query scale, the difference in the bill versus closed top-tier models can be large enough to decide the choice by itself.
Weaknesses
- The model's origin raises real questions about data and censorship. A Chinese corporation is behind the project, which for some companies and institutions is a hard entry barrier due to compliance and policy. In API applications, you also need to expect that some topics may be filtered or avoided according to local requirements, and that's not always transparent.
- Polish is supported, but you can still feel the distance from the Western top tier. In more difficult, nuanced texts, the model can be slightly less natural and precise than the best Western models. This doesn't disqualify it for Polish tasks, but if you care about perfect Polish, you'll notice the difference.
- Open weights sound great until you calculate how much self-hosting actually costs. Larger variants need serious hardware and expertise to deploy and maintain sensibly. For a solo developer or small company without DevOps infrastructure, using an API is often more convenient and cheaper in practice, which partially negates the advantage of openness.
Claude (Anthropic)
8.4/10
ChatGPT (OpenAI)
8.4/10
Gemini (Google)
8.1/10
Grok (xAI)
7.1/10
DeepSeek
7.0/10
Perplexity
7.9/10
Midjourney
6.6/10
Veo 3 (Google)
7.9/10
Kling
7.0/10
Seedream
7.4/10
Flux
7.2/10
Stable Diffusion
6.4/10