4 ms·
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
by ryan_j_naughton 2y ago
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.
- yawnxyz 2y agoI love jsonlines but csvs are way more compact, since you don't have to repeat the column name for every line of data
- ianburrell 2y agoYou 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.
- sam_perez 2y agoI think the fact that a human can mostly just read csvs is an important part of their adoption, too.
- jessekv 2y agoRather 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.