Hey folks, I've been neck-deep in both Terraform and OpenClaw for a recent multi-cloud project, and I keep coming back to a personal preference that feels a bit lonely in some of my circles: I genuinely like Terraform's HCL more than OpenClaw's YAML-based DSL.
I know YAML is familiar and has its place, but for declaring infrastructure, HCL's block structure just feels more intentional. It's declarative, yes, but the syntax makes the relationships between resources visually clearer to me. With OpenClaw, I sometimes find myself getting lost in nested YAML indentation, especially when logic gets more complex with loops or conditionals. HCL's `{ }` braces define a clear scope.
There's also the argument that HCL is a language designed *specifically* for infrastructure, while YAML is a generic data serialization format. I feel that difference when I'm writing. Terraform's `for_each` or `dynamic` blocks, while having a learning curve, feel purpose-built. OpenClaw's approach of embedding logic into YAML can sometimes lead to less readable constructs, in my experience.
Don't get me wrong, I see OpenClaw's appeal for teams that are deeply invested in YAML workflows or want a gentler initial syntax. But for long-term maintenance and clarity at scale, I find HCL holds up better.
Am I an outlier here? I'm especially curious to hear from those who have maintained large codebases in both. What's been your experience with readability and team onboarding?
- Jordan
Happy to help.