Society if the JSON standards included proper comments

Any standards.

We will always be in the stone age for they're will always be XML somewhere.

But why. It's data. You don't comment PNG data either.

@nitwhiz http://libpng.org/pub/png/...

@Pyjong whatever you want to say, the word "comment" isn't even once on this page.

@nitwhiz no but the value representation is

@nitwhiz ah I see, only code comments count here, ok my bad

@Pyjong yeah, i mean an example for visible comments within machine read data.
That you as human can edit JSON is just a plus, not something you should rely on imo.

Not exactly true.... Shitty devs remain shitty... Most programming languages have comments... Most devs never use them... It at least well enough so that other ppl can understand them

@PlatinumFire is XML really that bad?

@iSwimInTheC yes

@iSwimInTheC Yes, it's overhead is far higher in both increased size of payload and increased complexity of decoding. These two factors make it a demonstrably interior structure for data transmission.

@PlatinumFire how is this different than transmitting HTML?

@iSwimInTheC The scenario on topic here refers to JSON, as such I was specifying the use of XML in data transmission like in SOAP.

@PlatinumFire ah, yes you are right. In terms of structure between json and XML, does XML arguably have better structuring. Especially when dealing with nesting?

jsonc Anybody ?

@dder if it was part of the official JSON standard, but as it is right now... Ehhhhh

Also I'd rather not have // for comments, but only /* */

What would comments in JSON files actually say?

Doesn't a comment above a not descriptive enough key in your config to be read by the machine - not you - show the lack of proper documentation in form of a readme or shit like that?

Take php.ini as an example. This file is more comment then config, wtf is this.