> The daemon that runs in the background and is responsible for controlling the services is shepherd, while the user interface tool is called herd: it’s the command that allows you to actually herd your daemons
It seems strange the the herd controls the shepherd, but I guess it fits in well with GNU's user empowerment philosophy.
I'm very much a parenthesis-ophobe, but things like init configuration is a niche guile seems to be perfect for. It's terse enough to replace ini's, it's complex enough to provide structure like xml or json, it's an actual language so no one ends up writing their own and it's trivial to embed, like like lua.
I decided to port all my old perl scripts to guile scheme recently and got to add a bunch of nicities (like properly cleaning up on ctrl-c). Not because I really needed to, but because I haven't written perl seriously since 2010 and updating the scripts has started becoming hard.
The guile manual is pretty nice, but having something like this will always help people get started. For people that don't know about things like how non-local exits work getting started and doing it correctly can really take some time to figure out.
Guile-WM is a very neat project and fun to hack on since, like Emacs, you can edit it while it runs. It needs some more love to be usable for me as my daily driver, though. If I could only figure out the cause of a couple of bugs, things would be good enough for me.
Did you also know that it actually spawns the `sjeng` command line binary as an NSTask and attaches to stdin and stdout. So basically it’s just a fancy GUI around the Text based UI :)
loads instantaneously, simple config, fully-keyboard driven, vim-like bindings, great to use from the command line or terminal-based file managers like ranger.
Scsh: There was a whole lot of noise and some code about supporting Scsh on Guile early last decade, as there was for PLT Scheme, but both seem to have run out of steam. I think that replicating Scsh is harder than it looked at first.
I'm really pleased to see the work on the command language and bytecode interpreter. Scsh is something I've built a few times, but never got into. First the sounds of progress on the Emacs/guile front and now this look positive: it's a good time to take another look at Guile.
> The daemon that runs in the background and is responsible for controlling the services is shepherd, while the user interface tool is called herd: it’s the command that allows you to actually herd your daemons
It seems strange the the herd controls the shepherd, but I guess it fits in well with GNU's user empowerment philosophy.
I'm very much a parenthesis-ophobe, but things like init configuration is a niche guile seems to be perfect for. It's terse enough to replace ini's, it's complex enough to provide structure like xml or json, it's an actual language so no one ends up writing their own and it's trivial to embed, like like lua.
reply