It is not intended to be used for machine-to-machine communication.
YAML is not supported by a lot of enterprise software (example: Azure pipelines supports it but Power Automate does not). JSON, XML, CSV, or failing that Text are the safe bets. We use a few options for reading or building presentation layers quickly. Ultimately the idea is to move data around in a way that is friendly to our current and future applications.
It’s absolutely trivial to convert either format to json if necessary. The real killer for me with json is the lack of comments. Human-maintained files absolutely need comments.
That’s why my business only uses pure, crisp .txt files. If I can’t open it in notepad, I don’t want it!
I have unironically been preaching the powers of text and JSON, and have some converts. Universal compatibility is great.
Json is a garbage format for anything that’s meant to ever be touched by a human. At least use yaml or json5.
In the first paragraph of JSON5’s site:
YAML is not supported by a lot of enterprise software (example: Azure pipelines supports it but Power Automate does not). JSON, XML, CSV, or failing that Text are the safe bets. We use a few options for reading or building presentation layers quickly. Ultimately the idea is to move data around in a way that is friendly to our current and future applications.
It’s absolutely trivial to convert either format to json if necessary. The real killer for me with json is the lack of comments. Human-maintained files absolutely need comments.
With markdown or asciidoctor or restext or … you get both worlds.
Fuck it! I’m in!