I'm rapidly coming around to the idea that Three.js is the wrong choice for browser-based 3D apps built with AI. Three.js is an amazing library, and if you're building by hand it's immensely useful due to the DX, but you don't need it when Claude is writing the code and it's a 0.5MB overhead your game doesn't need.
I've built a bunch of things on ogl.js and brought the page weight of typical simple game under 100KB, and I've started removing the libraries entirely now. Claude made me a fantastic path tracer last weekend. No libraries needed.
I'm rapidly coming around to the idea that Three.js is the wrong choice for browser-based 3D apps built with AI. Three.js is an amazing library, and if you're building by hand it's immensely useful due to the DX, but you don't need it when Claude is writing the code and it's a 0.5MB overhead your game doesn't need.
I've built a bunch of things on ogl.js and brought the page weight of typical simple game under 100KB, and I've started removing the libraries entirely now. Claude made me a fantastic path tracer last weekend. No libraries needed.