I will not write a config management system in rust, accepting declarative policy in UCL, with extensable policy and resource definitions available in iolang, with a wrapper to accept terraform or shell providers.
Even though I want the performance and correctness of cfengine, the composable extension power of chef or puppet, and the ease of use of ansible and salt.
But without the agony of cfengine’s lack of expressiveness, heavy weight of chef (esp server) and the YAML of YAML.
Nope nope nope

@robdaemon Hashicorp HCL was originally based on a very unfinished implementation of UCL in go. They discussed using the actual libucl, but dismissed it because cgo build were more annoying then. But they quickly diverged, and even rejected patches to improve the parser to be closer to UCL, especially its JavaScript compatibility.
And modern HCL2 adds higher order features that are toeing the line of non-declarative; also separated the templating language into a separate parsing phase

@josephholsten I would use it.

@alpha Well sure, so would I! But I don’t know the intermediate steps enough to throw together a prototype in an afternoon.