3 ms·

You post a comment describing one alternative as "simpler" and "easier to read" compared to another. Respondent lists five specific reasons in support of the o

• krapp 8y ago
  No comments is... fair. That does put a limit on the legibility of JSON files, unless you want to count dumb hacks like comment strings. Having to quote strings in JSON, however is still simpler than the multitude of ways strings can be declared in YAML. You know a string is a string in JSON because of the quotes... knowing whether something is a string or not in context is more difficult in YAML because of the more complex syntax. You can learn the entire syntax of JSON in minutes. Objects, arrays, string keys, and a few primitive types... that's it. How long would it take to learn all of YAML? How explicit is its syntax versus JSON? Of course JSON is far simpler, and being simpler, it's easier to read. I dismissed "inane comma requirements" as an opinion, not everything the commenter said. The only reason it's "inane" is because the commenter doesn't like it personally. Not having multiline strings, to me, doesn't affect readability much at all, although it is unfortunate. Turn on text wrapping in your editor, it's the same thing. Typing support doesn't affect readability either. I'd like to have a date type in JSON too but 2013-03-01T16:15:09+01:00 or whatever is just as readable as "2013-03-01T16:15:09+01:00"