Is code-native 3D about to undergo a Cambrian explosion?
And if that happens, what emergent use cases will we witness? E.g. on-demand 3D, or smart 3D objects that automatically optimize for target environments, etc?
A couple of years ago, I got deeply interested in 3D represented as software, instead of static meshes. More recently, I also built a code-native 3D generation project to explore this line of thinking.
Building it made me realize:
(i) LLMs are increasingly becoming better spatial coders. They're naturally synthesizing sophisticated 3D via code, rather than attempting to output raw vertex data.
(ii) There is an emerging niche of users leveraging Three.js, Python, or C# specifically for dynamic, AI-driven generation at runtime.
So it seems to me we're moving away from pipelines where code just loads a file, toward runtime compilation where code is the file.
If LLMs take the reins of programmable 3D, what happens to the traditional graphics stack?
Comments URL: [https://news.ycombinator.com/item?id=49440962](https://news.ycombinator.com/item?id=49440962)
Points: 1