Everyone of us was a beginner at some point. The first time we came across CSV format we likely typed it in notepad by hand. A lot of issues with CSVs are also sometimes troubleshooted by hand-- by manually fixing a quote or a comma.
There is value is the ability to do this level of editing and troubleshooting.
> The first time we came across CSV format we likely typed it in notepad by hand.
Again, I'm not saying CSVs aren't edited by hand in a text editor, I'm saying they aren't created from scratch in a text editor, even by beginners. USVs are easy to edit in a text editor, too, and I tried viewing and editing USVs with a couple different fonts and had no problems.
Nobody can type up a GIF image, or Word document in a Notepad, yet files of both those formats exist. The answer obviously is tooling.
If a format with sane separators was common, so would editors that could edit that format be.
If a format with sane separators was common, so would editors that could edit that format be
Sure, but that's a hypothetical future editor, not something that currently exists.
Edit to add: I also disagree with "sane" in that context. New separators won't solve anything. You'll always need escaping/encoding/encapsulation; get that right and everything else follows. JSON is comma-separated and does just fine.
There is value is the ability to do this level of editing and troubleshooting.