4 ms·
This "easier" format is actually more "complex". JSON can be described with just a couple of simple rules (http://json.org/ http://json.org/ ), while this forma
by IvanK_net 11y ago
This "easier" format is actually more "complex". JSON can be described with just a couple of simple rules (http://json.org/ http://json.org/ ), while this format adds many new rules (e.g. for doing same things in multiple ways). The more rules you have, the more things you have to remember, the harder it is to find the reason of the problem.
BTW. it is very simple to do comments in JSON :) You can just add
"comment1" : "This is my comment",
to any object, it will be ignored by software that processes your file.
- mort96 11y agoI kind of like doing comments like this: "#": " my comment"
- ZenPsycho 11y agothe problem with that one is that some parsers have a meltdown if they encounter duplicate keys. sigh
- abraae 11y agoHa ha, I do exactly the same thing. Lack of comments is really the only beef I have with Json (well, no multi line text too I suppose). A new spec that just addressed those alone would be great.