>> It's relatively easy to parse (while not as easy as a sane well-specified version of CSV would be). > Wrong. CSV is horrible to parse with its string quotin

>> It's relatively easy to parse (while not as easy as a sane well-specified version of CSV would be). > Wrong. CSV is horrible to parse with its string quoting rules. I made a reasonable attempt at preventing exactly this misunderstanding, but I guess if people want to misread you they will. > Nobody is talking about application logic here but you. The application logic (I'm including internal data representation here) is the meat of all efforts, so you should absolutely be considering it, instead of needlessly putting isolated efforts in optimization of side actors. Parsing JSON should IMHO be a total side concern, and using an oversized library like the one we're talking about fails to acknowledge that. Such a library is either a wasted effort (if its data types aren't used throughout the application), or else (if they are) use of the library leads to massive problems down the road.