Ooohhh this is a cool model. I really like the style. Also cool project lol.
A CSS 3D engine for the DOM. Renders polygon meshes in HTML by leveraging matrix3d transforms.
Submitted 2 days ago by cm0002@libretechni.ca to programming@programming.dev
https://github.com/LayoutitStudio/polycss
Comments
AI_toothbrush@lemmy.zip 1 day ago
MonkderVierte@lemmy.zip 2 days ago
Just because you can, doesn’t mean you should.
Kissaki@programming.dev 1 day ago
But someone should!
xthexder@l.sw0.com 2 days ago
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?
rizzothesmall@sh.itjust.works 2 days ago
Why store polies in tiny byte spans when you can store them in up to a KB each of markup?
Kissaki@programming.dev 1 day ago
Inspected, looks like even hidden-behind elements receive matrix transformation updates.
Image
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.