I agree that JSONL is the spiritual successor of CSV with most of the benefits and almost none of the drawbacks. It has a downside though: wherever JSON itself

I agree that JSONL is the spiritual successor of CSV with most of the benefits and almost none of the drawbacks. It has a downside though: wherever JSON itself is used, it tends to be a few kilobytes at least (from an API response, for example). If you collect those in a JSONL file the lines tend to get verrrry long and difficult to edit. CSV files are more compact. JSONL files are a lot easier to work with though. Less headaches.