robinvdvleuten

Awesome! Not only that one can build this in JavaScript, but also that your browser on a mobile phone can render this.

So much hours spent with Kid Pix at our macintosh back in the days! Still remember all the sounds and effects, especially this weird magic gum thing.

The observability part is the most interesting bit to me.

With agent systems, logs get bad pretty quickly. You want to know what is alive, what spawned what, what it's waiting on, what retried, what died, etc.

Since this is Elixir, are you planning to show the actual BEAM process/supervision structure in WeaveScope, or mostly the higher-level workflow graph?

Feels like both are useful. The graph shows what you meant to run, the process tree shows what is actually running.

This is a neat LiveView use case. The bit that jumped out to me is "each game as its own process", which feels very BEAM-y in the good way.

Curious how you're handling abandoned games. Do they just sit around until some timeout kills them, or are you persisting after each move so they can be rebuilt after a deploy/restart?

What do you know now then?