YAML is usually considered human readable and writable. Thus people like it for config.

JSON is of course technically both of these, but less so to make it a good config format.

INI has a shallow data model, but is good enough for most config, and less impervious to syntax errors than YAML and JSON.

YAML is probably better for config as soon as you need much more than a flat hash model.

That's my quick PoV.


On Thu, Jun 26, 2014 at 9:51 AM, Trans <> wrote:
On Thu, Jun 26, 2014 at 11:35 AM, Susu Laird <> wrote:
Well, how's this any better than json?

YAML is more readable, and thus also more easily writable.

Content wise, they would be nearly alike, except for Date/Times (put another tick in the YAML column).


Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
Yaml-core mailing list