News for hackers. Stuff that matters.
Re:Problems with CSVs (2016) by dtech on Wednesday April 11, 2018 @08:57AM (#16810616)
XML, JSON, any specified format is a better machine-to-machine format than CSV.

I've seen the JSON-object-per-newline pattern a few times, but why not use a JSON array then? Then the whole file remains valid JSON.

Re:Problems with CSVs (2016) by dalailambda on Wednesday April 11, 2018 @09:14AM (#16810746)
In my experience the reason for a JSON object per line is because a tool can then split the entire file by newlines and have a list of objects to start parsing/processing in parallel, which avoids having to parse the entire file up front to get usable data, and lets the tool start processing things while some data is still being parsed.
Re:Problems with CSVs (2016) by ex3ndr on Wednesday April 11, 2018 @09:05AM (#16810680)
This is just easier to implement line-by-line processing than hacking into JSON parsers for this.