> "To that end, configuration is defined in a YAML file called the request collection"

Genuine question, why do people use YAML? I've been using it a little bit recently (reading existing documents, not writing my own), and it just seems like a more overcomplicated and less human-readable version of JSON? With potential security vulnerabilities?

▲ mystifyingpoi 43 minutes ago | parent | next [-]

> less human-readable version of JSON

Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.

	▲	voidUpdate 29 minutes ago \| parent [-]
		Indentation based structure isn't really a good thing in my eyes, where the format of the document encodes semantic meaning. With JSON, you can display it how you want, and because it's bracketed it will still encode the same data. Also I really don't like the hyphen notation... This is very unreadable to me: `- a - b: c - - d`

▲ amazingman an hour ago | parent | prev | next [-]

People use YAML because a bunch of other people use YAML. Whatever its warts, there's no use resisting it.

▲ kalaksi an hour ago | parent | prev | next [-]

If not using any esoteric features, it's more human readable (imo), easier to write, can have comments and has some useful features like different kind of multi-line values. JSON is valid YAML, by the way.

▲ bschwindHN an hour ago | parent | prev | next [-]

> it just seems like a more overcomplicated

Because people LOVE overcomplicated shit. You see it happen everywhere.

	▲	kalaksi an hour ago \| parent [-]
		I don't think that's it

▲ speed_spread an hour ago | parent | prev [-]

Because as long as you stay away from anchors and inline JSON, YAML is a perfectly workable, structured, human-readable format that supports comments.