I mean, they're pretty much the same right? You can't abstract away the services and you need to pass arguments to the executable (ntpd in this case). I don't

I mean, they're pretty much the same right? You can't abstract away the services and you need to pass arguments to the executable (ntpd in this case). I don't see more or fewer issues, but I also don't see the value to using Scheme instead of a conf. file like format. At the end, there's talk about adding the possibility to live reconfigure services, which is pretty cool but I don't really see what kind of users are targeted by that use-case, at least not regular users like me who's running Linux on a single laptop. The link at the end (https://spritely.institute/news/spritely-nlnet-grants-december-2023.html https://spritely.institute/news/spritely-nlnet-grants-decemb...) is IMO much more interesting since it would make it possible to orchestrate several machines and their services as well. If you have live reloading as well, I think it would make for good developer experience. My main gripe with Guile is its ergonomics and tooling: no LSP, no linter, no step-debugger that I know of and the docs are often unhelpful imo. Maybe I'm not Scheme brained enough but I think it's a shame because there are some really cool projects out there (anything https://spritely.institute/ https://spritely.institute/ really). P.S: I know that some people will tell me to get used to REPL based development which I think is fine for small-ish projects but I can't understand the flow one uses for larger projects where many components might need to talk to each other.