2 ms·
A counter example where the utility does output XML is https://man.netbsd.org/envstat.8 https://man.netbsd.org/envstat.8 There were some upvotes then a series
by 1vuio0pswjnm7 5y ago
A counter example where the utility does output XML is https://man.netbsd.org/envstat.8 https://man.netbsd.org/envstat.8
There were some upvotes then a series of downvotes as the top comment in this thread changed. Thus, opinion on this issue is mixed.
JSON of course stands for "object" notation. Once we start delimiting the "object" with a newline, or limit its size/length, it arguably starts to sound more like string and the problem of memory requirements is abated.
As the parent comment suggested, when the "object" notation is used for delimited JSON it's really not "JSON" anymore. Is it still describing "objects", or is it describing strings, with the addition of brackets, braces, commas, colons and more quotes. Let the reader decide.
It is reasonable to ask what was the purpose of JSON in the first place, and, if it was designed for sending data over a network, whether previous solutions like netstrings could accomplish the same things as delimited JSON.