The choice of Braille is very clever. I once failed a typography class for using Braille in a final design project that was supposed to create a sequence of images representing a visual story out of pure typography. This followed a 30 minute long argument with the professor during critique in which he asserted that Braille was not type. I countered that it was. It's charming to see it employed in this way.

The Braille trick has been used for ASCII art for awhile. In this case, I was more interested in it for subcharacter rendering of balls.

I didn't realize that, haven't thought about ASCII/ANSI art since the 90s, but the concept of using it for subcharacter animation is clever. Cheers.

[edit] Odd question. I have relatives in the Bay Area who I think spelled their name Wolfe. Their patriarch was named Eliot and survived Auschwitz. Any relation?

I'm from the East Coast.

Reading your workflow described in PROMPTS.md was insightful. I appreciate how much thought goes into each follow-up, including the manual steps after each invocation.

The prompts turned out significantly better this time!

I just wanted to chime in and thank you for sharing your prompts like that!

It feels like which prompts people are using (even from developers on the same team) is often opaque. It's a great learning resource for people to see under the hood of each other's AI coding workflows, and I hope to see more folks doing this.

(Link for anyone who wants to check them out): https://github.com/minimaxir/ballin/blob/main/PROMPTS.md

The effect reminds me of the classic Fishtro demo by Future Crew from 1992: https://www.youtube.com/watch?v=yUjRpLn2qWo

I remember that demo - thanks for the nostalgic flash back!

Claude, slopcode me an Omarchy screensaver using this. Make it so!

Incidentally I was thinking about adding some automated physics events so it could be viewed passively.

Likely not a computationally efficient screensaver, though.

Now, this makes me think of a thing I never knew I wanted: Plasma Pong, but in the terminal.

> For terminal compatability and accessibility reasons, Color Mode is disabled by default

Now i get it. Colors make UI inaccessible. So that's why Windows is Gray on Gray. And why the color icons were replaced with Gray on Gray icons.

Until now i regarded my above sentence as satire but, i need to face the reality. /s

The color contrast between the ANSI colors and the terminal backgrounds for some terminals make it so the colors are hard to see.