algernon is waiting for @iocaine to toot
@algernon@come-from.mad-scientist.club  ·  activity timestamp 3 weeks ago

Yesterday, after contemplating how to structure a possible YAML-based configuration for Nam-Shub of Enki, I was reminded that TOML exists. And iocaine uses it as its config format anyway, so why not use the same for Nam-Shub?

So I did some experimentation, and now I'm working on assembling a configuration from Nam-Shub.

Incidentally, I might also restructure the Config type the TOML will be deserialized into to follow a similar structure. That will also allow me to split up the big configuration.org file, and let the various features target references in it... or in other words: move the declaration of config options to the node that implements said feature, rather than having it in the monolithic configuration.org.
algernon is waiting for @iocaine to toot
@algernon@come-from.mad-scientist.club replied  ·  activity timestamp 3 weeks ago

So, this is a three step process:

  1. Make all configuration go through the Config type. Previously, most configuration went through it, but some used environment variables directly. Now the env vars are stored in Config. This part I'm done with!
  2. Restructure and split up configuration.org, as described in the previous toot.
  3. Load a TOML config, and adjust the configuration assembly to make use of it.

At the end of all this, my hope is that Nam-Shub of Enki will be much easier to consume for people other than myself.

I will need to write a HOWTO guide too, separate from the rendered org, so that the entire TOML config is on one page.
algernon is waiting for @iocaine to toot
@algernon@come-from.mad-scientist.club replied  ·  activity timestamp 3 weeks ago

The one problem with this is that it's been ages I listened to any of them. I keep getting distracted... just sit back, close my eyes, and immerse myself in the music.

Every song on this playlist is fantastic. This is not helping with moving Nam-Shub forward. Funnily, that might be quite fitting!

~21 more replies (not shown)
algernon is waiting for @iocaine to toot
@algernon@come-from.mad-scientist.club replied  ·  activity timestamp 3 weeks ago

It just hit me: storing everything in the Config, and making it able to load from TOML has a huge downside: it's reconstructed for every request. That's not good.

So after I'm done restructuring the config stuff, I'll kind of restructure it again: I'll find a way to construct it once during init, and store it forever for the main script.

Lua/Fennel can already do this, because there are globals there. But Nam-Shub of Enki is Roto. So I will be cheating a little: I'll introduce a globals context variable, similar to matchers. It too, will be turned into constants, but it will be able to hold various types, so in the main script, I'll re-assemble the Config type from these globals - or just use the globals directly... but I kindal like the convenience of the Config type, so I'm willing to pay a small price there.