> Sometimes CSV files themselves are ambiguous because they don't use any quoting so you end up with some lines that have more columns than others, and require

> Sometimes CSV files themselves are ambiguous because they don't use any quoting so you end up with some lines that have more columns than others, and require manual repair line-by-line by a human. It's wild that we haven't just started using unicode and line/group separator characters for tabular data instead of csv/tsv. Whoever decided to use a common semantic character as syntax is an evil, devious bastard. That said, there is one thing I like about CSV and similar formats: they are inherently tabular. You don't have to worry about someone adding sub-objects to your JSON (or replacing a primitive field with an object/array). Extra columns are brainless to add or process, but converting sub-data to a line is not.