Just because you can, doesn't mean you should.
this post was submitted on 01 Jun 2026
35 points (94.9% liked)
Programming
27160 readers
388 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
But someone should!
Why store polies in tiny byte spans when you can store them in up to a KB each of markup?
Inspected, looks like even hidden-behind elements receive matrix transformation updates.
Presumably, skipping those could increase performance? But maybe it's not possible with this approach. I haven't checked deeply. I guess it's infeasible.
The browser's compositor handles the 3D layering.
Ooohhh this is a cool model. I really like the style. Aldo cool project lol.
spoiler
What a strange concept. The demo is quite laggy on my phone, and has triangles constantly disappearing as it moves. Other online 3d viewers are able to load significantly larger models without any lag or graphical artifacts.
I don't think the way this is implemented it can realistically use much GPU acceleration at all. It's like taking all the vertex shaders and running them on the CPU, and then only using the GPU for triangle texture fill and depth testing... The hardware is right there, why avoid using it?