> No WebGL

Why is this an advantage? I have a GPU and I'd rather it was used. As-is, one of my CPU cores is pegged at 100% just rendering the landing page.

> > No WebGL

> Why

Sometimes hobby projects are a fun challenge because of the limitations you set for yourself. “No WebGL” (and “no canvas”) comes directly between “Render textured 3D meshes in the DOM” and “Each scene is a single <pre> you can…”. Why did I write some SQL to use TSQLs geometry types to draw a dragon curve fractal in SSMS way back when? Certainly not because it was an efficient use of the tech or my time!

How this challenge aspect translates to a project that (going by other comments) is largely vibe-coded escapes me a bit, if I asked an ML algorithm to complete a sudoku I wouldn't feel any sense of achievement, but each to their own.

> Why is this an advantage? I have a GPU and…

Away from the “because that was the challenge the maker set for themselves” aspect: WebGL does not always work, such as over most remote desktop solutions (there are of course ways to make the access it needs to the GPU possible, depending on the remoting option you are using, but one of those being configured is far from a given). This will continue to operate in those circumstances.

Presumably because its an intentional throwback to the era when most people didn't have a GPU?

When the topic is rendering 3d models using ASCII glyphs, we've already exited the realm of advantages and disadvantages. This is just supposed to be cool.

maybe to prove the output is purely text only?

heh, i came here to say basically the same thing