News for hackers. Stuff that matters.
Re:Why CSV is still king by ryan_j_naughton on Thursday August 01, 2024 @09:14PM (#41135266)
Eh, I'm skeptical of this statement.

CVS is explicitly about tabular data. JSON (including JSON5) is much more flexible. Flexibility can be great but also can be annoying. If you want tabular data, then a system that enables nesting isn't great.

Re:Why CSV is still king by yawnxyz on Thursday August 01, 2024 @10:57PM (#41135726)
I love jsonlines but csvs are way more compact, since you don't have to repeat the column name for every line of data
Re:Why CSV is still king by sam_perez on Thursday August 01, 2024 @11:39PM (#41135915)
I think the fact that a human can mostly just read csvs is an important part of their adoption, too.
Re:Why CSV is still king by ianburrell on Friday August 02, 2024 @11:55PM (#41144586)
You would write JSON arrays without names for tabular data. I don’t know if there is a standard way to do the header, but array of names would work. Or JSON Schema record.
Re:Why CSV is still king by jessekv on Friday August 02, 2024 @08:48AM (#41138424)
Rather than highlighting flexibility as the differentiator, I would say: CSV is for dense data, JSON is for sparse data. They are flexible in different ways. For example, CSV is very flexible when renaming a column title.