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?

Modern front-ends often need a tiny bit of server-rendered data to kick-start hydration or to configure a widget. The usual answer is an inline <script> that hydrates a global variable—but that approach triggers strict Content Security Policies, can’t be cached independently, and forces you to hand-roll parsing and error handling for every page. json-from-script smooths out that workflow by treating <script type="application/json"> tags as a simple, declarative data transport that is safe under CSP.

There are some other countries using this format as well. I know at least Belgium, Luxembourg, Ireland, Spain, Germany, Denmark, Sweden, Finland, and Hungary, though compatibility can vary.

If you are really into the hardware stuff, you can combine this package quite easily with Elixir’s nerves and make your own esp32 p1 reader yourself!

I own one as well and actually flashed it with my DSMR library combined with nerves. Another way is to let the slimmelezer-plus expose a TCP server and let Elixir’s genserver just parse the incoming telegrams through this package (see the livebook examples)

You are totally right! But it would make the logic way more complex than it is right now. I have as "tussenvoegsel" already two words, but how to handle also last names containing two words as well.

Most of the time a distinct between first and last name is already enough for presentational purposes.