I have actually seen it in an XML file in the wild. Never quite understood why they did it. Anything they encoded into there, they could have just added a node for.
But it was an XML format that was widely used in a big company, so presumably somewhere someone wrote a shitty XML parser that can’t deal with additional nodes. Or they were just scared of touching the existing structure, I don’t know.
That’s my biggest peev about JSON actually. No comments!! WTH!
On one hand I agree, on the other hand I just know that some people would immediately abuse it and put relevant data into comments.
do they do that in xml? never seen that
I have actually seen it in an XML file in the wild. Never quite understood why they did it. Anything they encoded into there, they could have just added a node for.
But it was an XML format that was widely used in a big company, so presumably somewhere someone wrote a shitty XML parser that can’t deal with additional nodes. Or they were just scared of touching the existing structure, I don’t know.
This is why there are none, but I still think it’s dumb. Parsers can’t see comments anyways.
That’s assuming people actually use a parser and don’t build their own “parser” to read values manually.
And before anyone asks: Yes, I’ve known people who did exactly that and to this day I’m still traumatized by that discovery.
But yes, comments would’ve been nice.
There’s comments in the specs and a bunch of parsers that actually inore //
I don’t see comments in the spec?
json spec draft 7