Similar to the panic over DeepSeek R1, some uneducated people think Kimi K3’s use of linear attention (KDA) is bad for NVIDIA, HBM, DRAM, and networking because it has relatively lower KV-cache requirements. The opposite is true, and we explain why below. 👇️ 1/8🧵
@snmishra311 When you’ve got well understood task distribution, a lot of observability, low latency requirements, and (at least today) some research expertise on the team
Big news: Kimi-K3 by @Kimi_Moonshot is now #1 in the Frontend Code Arena with 1679 pts, surpassing Claude Fable 5.
This is a 17-place jump from Kimi-k2.6 (#18 -> #1).
In Frontend, Kimi-K3 ranked #1 in 6 of 7 domains: Brand & Marketing, Reference-Based Design, Data & Analytics, Consumer Product, Simulations, and Content Creation Tools, landing #2 only in Gaming behind Fable 5.
The full model weights will be released by July 27.
Congrats to the @Kimi_Moonshot team on this major milestone!
@quxiaoyin@thinkymachines@AnthropicAI Love Tinker and bullish on what they’re doing to make post-training accessible but find it hard to believe enterprises will be thinking of post-training before just building agents that work (the latter biases users towards Claude)
@fluorane@appliedcompute@trajectorylabs@EngramLab I'd guess there are probably only a handful of companies today (like Harvey, Decagon) with evals, rubrics, agent traces already set up + have already tried to squeeze performance through methods that don't touch model weights