4 ms·
I think a takeaway could also be not to give people options when making a human-readable format. "you always need quotes, they're not optional" solves the comma
by asddubs 3y ago
I think a takeaway could also be not to give people options when making a human-readable format. "you always need quotes, they're not optional" solves the comma problem. "the delimiter is always a comma" solves the delimiter problem. json has also fared better than csv, I'd say.
- emj 3y agoThat makes the delimiter "," which is ugly so someone is just going to use , instead and you are back to square one.
- asddubs 3y agothis is only the case because this was allowed from day 1. If no one ever allowed this to begin with, that just wouldn't work. Of course this is speaking in hypotheticals, but my point is a more general one about specifications of human-readable formats. no one ever attempts to use strings without quotes in json, because then you would be incompatible with everything. There's compatibility issues, but they're far more subtle edge cases