Hacker News new | past | comments | ask | show | jobs | submit login

Sure, could be simpler, but there's a spec and multiple implementations: https://www.rfc-editor.org/rfc/rfc4180.html And the spec is ~5 pages.

Not sure why NDJSON is considered simpler, as json objects can be arbitrarily nested. Breaking into records is easier, but parsing is harder.




(ND)JSON is simpler because people actually follow the spec, unlike with CSV.


People violate the JSON spec all the time.

And following the CSV spec is much easier than following the JSON spec. And there's only like three edge cases.


> And there's only like three edge cases.

Unless you involve MS Excel or, worse, MS Excel on macOS. OTOH, pitfalls are: UTF-8 BOM, comma vs semicolon, single vs double quote, multiline cell content and escaping, escaping in general...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: