Just one thought - code should not be driven by YAML, or in other words yaml configuration should be just configurations, nothing more - thus are simple and easy to read
As a result application changes should not be lost in yaml complexity
Agreed. I’m not trying to make YAML more powerful, more trying to make the complexity that already exists easier to review (K8s/CI configs already live in YAML).
In my head it’s “diff + guardrails” so behavior changes don’t get buried in big files.
Always wonder what’s bitten people more.... unreadable diffs, or YAML being used like a programming language (templating/anchors/etc.)?
gMan1|1 month ago
In my head it’s “diff + guardrails” so behavior changes don’t get buried in big files.
Always wonder what’s bitten people more.... unreadable diffs, or YAML being used like a programming language (templating/anchors/etc.)?