The Bugged Dev (@thebuggeddev) “My honest take on @Kimi_Moonshot K3 👀 As soon as I got access to Kimi, I put it” — TopicDigg

My honest take on @Kimi_Moonshot K3 👀 As soon as I got access to Kimi, I put it through the exact same 3D football stadium challenge I had previously given Claude Fable 5. Fable 5 finished in under an hour. Kimi took almost 3 hours 🥵 At first, that was a very bad impression but i decided to see what's taking it this much of time. It was running E2E tests, validating desktop, tablet, and mobile, taking screenshots, finding failures, fixing them, even adapting for low end hardware and low FPS before moving on. All these that Fable 5 never did. None of it because it wasn't able to run this WebGL app on a headless browser. Kimi also shipped a clean React + Three.js codebase with proper components while Fable, as you might have checked codebase, generated one big HTML file with everything stuffed in. With all of this happening, it felt like I was doing more "Vibe Coding" with Fable 5 and more "Vibe Engineering" with Kimi K3. It feels like it's spending more time making sure the code actually works and easily scalable. Really impressed so far. More Kimi K3 experiments coming soon. Code (Kimi): Code (Fable): Live (Kimi hosted):