Programming

{
    "columns": ["id", "name", "age"],
    "rows": [
        [1, "bob", 44], [2, "alice", 7], ...
    ]
}

There ya go, problem solved without the unparseable ambiguity of CSV

Please stop using CSV.

No:

• CSV isn't good for anything unless you exactly specify the dialect. CSV is unstandardized, so you can't parse arbitrary CSV files correctly.
• you don't have to serialize tables to JSON in the “list of named records” format

Just user Zarr or so for array data. A table with more than 200 rows isn't ”human readable” anyway.

Yes..but compression

And with csv you just gotta pray that you're parser parses the same as their writer..and that their writer was correctly implemented..and they set the settings correctly

Exactly. I've seen so much data destroyed silently deep in some bioinformatics pipeline due to this that I've just become an anti CSV advocate.

Use literally anything else that doesn't need out of band “I'm using this dialect” information that has to match to prevent data loss.