News for hackers. Stuff that matters.
Re:Why are we templating YAML? by amanzi on Thursday February 07, 2019 @05:00PM (#19109013)
Writing YAML is not easy for end-users. The indentation--especially in large files--is really difficult to keep track of, and some really basic stuff like when to quote strings is not consistent at all.
Re:Why are we templating YAML? by shirakawasuna on Thursday February 07, 2019 @05:31PM (#19109280)
It definitely is. You have no idea how intimidating an equivalent JSON file would be for a new user creating a pretty simple k8s setup.

YAML hides most of the scary brackets and quotes so that new users can focus on copy-and-pasting semantic tidbits.

That said... I don't like YAML...

Re:Why are we templating YAML? by mixmastamyk on Thursday February 07, 2019 @05:15PM (#19109150)
Nope, indentation is not a problem with indentation guides. A misplaced comma in a JSON file however kills it, gets me every time I have to write it by hand.

Also, it is true YAML has too many features, though I find they are typically ignored or disabled.

Re:Why are we templating YAML? by krapp on Thursday February 07, 2019 @05:20PM (#19109181)
A misplaced comma is also not a problem in an editor with syntax highlighting, but between the two, indentation could take longer to fix.
Re:Why are we templating YAML? by mixmastamyk on Thursday February 07, 2019 @05:25PM (#19109240)
Syntax highlighting doesn't count commas. The problem is JSON doesn't allow trailing commas, so adding or reordering frequently results in a difficult to diagnose error.
Re:Why are we templating YAML? by krapp on Thursday February 07, 2019 @05:33PM (#19109306)
Finding out if a set ends in a comma or not still makes it easier to debug than YAML.
Re:Why are we templating YAML? by mixmastamyk on Thursday February 07, 2019 @05:46PM (#19109428)
Not my experience, 10x more trouble with long JSON.