For "human-friendliness" (eg. hand-edited configs), I'm all in with YAML. AFAIC, JSON is strictly for machine to machine data transmission. While I think the

For "human-friendliness" (eg. hand-edited configs), I'm all in with YAML. AFAIC, JSON is strictly for machine to machine data transmission. While I think the idea is neat, a data language should not include processing logic. It's a wash where the constraints get specified, and in my experience, a single point of implementation is far more maintainable.