On 11/12/2017 10:42 PM, Gert Doering wrote: > On Sun, Nov 12, 2017 at 12:21:06PM -0500, Selva wrote: >> One of the niceties of JSON is its readability which is greatly reduced >> if formatted without line breaks. > > +1 > > the difference in efficienty is not large, but "human readability for > manual proofreading" is good.
Selva, Gert, You know, the funny thing is that my main reason for implementing JSON support for status was to have it easily _machine_ readable, for higher level programming languages where JSON is "first class citizen", and not primarily human readability. Besides you could easily do this to make JSON human readable: $ cat /path/to/status.json | python -mjson.tool Thinking some more about it now, it doesn't really make sense to implement JSON at all, because CSV _is_ actually meant to be machine readable and a lot more efficient in the amount of data it uses (much less duplication). So it seems my reasons for implementing JSON support seems to completely miss the point. For machine readable output it would make more sense to use a binary format instead of JSON. What do you guys think? Are there any other reasons to implement JSON support? Cheers, François
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
