News for hackers. Stuff that matters.

A comment on Comma Separated JSON.

Re:Comma Separated JSON by ctulek on Wednesday June 22, 2016 @07:54AM (#11953124)
If you are using a proper CSV library you don't have any of the problems this format is trying to solve. The CSV format does not have any issues mentioned, it is either a buggy CSV library or some lazzy developer who thinks CSV is just fields separated with comma writing 2 line of code instead of using a proper CSV library.
[ Parent | on HN ]
Re:Comma Separated JSON by danso on Wednesday June 22, 2016 @08:02AM (#11953171)
Which CSV library is able to infer that a value is a number instead of a string?
[ Parent | on HN ]
Re:Comma Separated JSON by ctulek on Thursday June 23, 2016 @01:15AM (#11958989)
CSV for sure requires a convention to be shared between the producer and the consumer of the data. Once you have that I don't think you will need to deal with this problem.

To be honest, what I didn't like is the tone of the article. It is just that this statement is wrong: "But the problem is that CSV isn't really a well defined file format with a well defined syntax." There is RFC 4180.

[ Parent | on HN ]