> About CSV, while I'm not opposed to it we have a practice guideline to use
> JSON for machine-parseable output. One reason is that JSON is better at
> being self-describing - the field names give you clues that CSV doesn't.
CSV is readable by eye without a lot of effort. JSON is close to encrypted.
Many CSV files have a comment line on top with the field names.
These are my opinions. I hate spam.
devel mailing list