69 lines
4.2 KiB
Markdown
69 lines
4.2 KiB
Markdown
|
---
|
|||
|
|
type: xpost
|
|||
|
|
source_url: https://x.com/thebuggeddev/status/2079185808305823940
|
|||
|
|
retrieved: 2026-07-20
|
|||
|
|
author: "@thebuggeddev"
|
|||
|
|
author_name: "The Bugged Dev"
|
|||
|
|
is_thread: false
|
|||
|
|
like_count: 464
|
|||
|
|
repost_count: 38
|
|||
|
|
quote_count: 4
|
|||
|
|
reply_count: 24
|
|||
|
|
bookmark_count: 240
|
|||
|
|
view_count: 46500
|
|||
|
|
tags: [kimi-k3, fable-5, anthropic, moonshot-ai, vibe-coding, vibe-engineering, coding-benchmark, real-world-test, react, threejs, e2e-testing, responsive, quality]
|
|||
|
|
people: []
|
|||
|
|
institutions: [moonshot-ai, anthropic]
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
# The Bugged Dev: Kimi K3 vs Fable 5 — Real-World 3D Stadium Coding Challenge
|
|||
|
|
|
|||
|
|
**Source:** [X-Post by @thebuggeddev](https://x.com/thebuggeddev/status/2079185808305823940)
|
|||
|
|
**Posted:** 2026-07-20
|
|||
|
|
**Stats:** 464 likes | 38 reposts | 4 quotes | 24 replies | 240 bookmarks | 46.5K views
|
|||
|
|
|
|||
|
|
## Post Content
|
|||
|
|
|
|||
|
|
> Real-world comparison of Kimi K3 vs Claude Fable 5 on the same 3D football stadium coding challenge.
|
|||
|
|
>
|
|||
|
|
> Fable 5 finished in under 1 hour. Kimi K3 took almost 3 hours.
|
|||
|
|
>
|
|||
|
|
> But Kimi did E2E testing, validated desktop/tablet/mobile, took screenshots, found and fixed failures, adapted for low-end hardware and low FPS — all things Fable never did.
|
|||
|
|
>
|
|||
|
|
> Kimi shipped clean React + Three.js codebase with proper components; Fable generated one big HTML file with everything stuffed in.
|
|||
|
|
>
|
|||
|
|
> Conclusion: "Vibe Coding" with Fable 5 vs "Vibe Engineering" with Kimi K3. Kimi spends more time making sure code actually works and is scalable.
|
|||
|
|
|
|||
|
|
## Links
|
|||
|
|
|
|||
|
|
- **Code (Kimi K3):** https://t.co/IcLLZOb5mM
|
|||
|
|
- **Code (Fable 5):** https://t.co/6siJHap4fb
|
|||
|
|
- **Live Demo (Kimi K3):** https://el-clasico-4ts.pages.dev/
|
|||
|
|
|
|||
|
|
## Key Takeaways
|
|||
|
|
|
|||
|
|
1. **Speed vs. Thoroughness:** Fable 5 was 3× faster (under 1h vs ~3h), but Kimi K3 used the extra time for comprehensive quality assurance — E2E testing, cross-device validation, screenshots, failure detection and fixing, low-end hardware adaptation.
|
|||
|
|
2. **Code Architecture:** Kimi K3 produced a clean React + Three.js codebase with proper component separation. Fable 5 generated a single monolithic HTML file with everything stuffed in — faster but structurally inferior.
|
|||
|
|
3. **"Vibe Coding" vs. "Vibe Engineering":** A useful framework distinction. Vibe Coding (Fable 5) = fast, spontaneous generation. Vibe Engineering (Kimi K3) = thorough, validated, scalable code production. The extra time is quality investment, not slowness.
|
|||
|
|
4. **Bookmark-heavy engagement:** 240 bookmarks vs 464 likes suggests developers are saving this as a reference — high practical value signal.
|
|||
|
|
|
|||
|
|
## Analysis (Hector, OME group)
|
|||
|
|
|
|||
|
|
This comparison complements the earlier @bridgemindai post about Moonshot's customer-first capacity management. Kimi K3 isn't just faster (100% speed improvement reported earlier from capacity event) — it's more thorough. The extra time is quality investment, not slowness.
|
|||
|
|
|
|||
|
|
**Combined signals from Moonshot:**
|
|||
|
|
- **Business model:** Customer-first capacity management (stopped new subscriptions instead of throttling existing users)
|
|||
|
|
- **Product quality:** Engineering thoroughness over speed (E2E testing, responsive validation, proper code architecture)
|
|||
|
|
- **Framework contribution:** "Vibe Engineering" as a distinct concept from "Vibe Coding" — Moonshot is building both a customer-friendly business model AND a product that prioritizes engineering quality over speed.
|
|||
|
|
|
|||
|
|
The "Vibe Engineering" vs. "Vibe Coding" distinction is a useful framework that extends Tielke's "Vibe Coding vs. Enterprise Software Development" taxonomy. Where Tielke contrasted vibe coding with enterprise process, @thebuggeddev shows the distinction exists *within* AI-assisted development itself — between fast-but-shallow and thorough-but-slower approaches.
|
|||
|
|
|
|||
|
|
## Cross-References
|
|||
|
|
|
|||
|
|
- [[../../wiki/concepts/llm/kimi-k3.md]] — Kimi K3 model page
|
|||
|
|
- [[../../wiki/concepts/llm/fable-5-anthropic.md]] — Fable 5 model page
|
|||
|
|
- [[../../wiki/concepts/llm/vibe-coding-vs-enterprise.md]] — Tielke's Vibe Coding vs. Enterprise framework
|
|||
|
|
- [[../../wiki/institutions/moonshot-ai.md]] — Moonshot AI
|
|||
|
|
- [[../../wiki/institutions/anthropic.md]] — Anthropic
|
|||
|
|
- [[../../wiki/concepts/llm/coding-benchmark-price-performance.md]] — Coding benchmark comparison
|
|||
|
|
- [[../../wiki/concepts/llm/real-world-coding-showdown.md]] — Real-world coding methodology
|