I love Json format. It is so simple, powerful, easy to read and all that good stuffs. There is only one thing I wish Json could support, that's commenting.

The problem is that people use it for configuration files. With npm package.json you can use the "//" key for a comment but it is ugly..
I kind of wish you didn't need quotes around everything in them.

Thats the reason i Like yaml

Comments were sacrificed for interoperability: https://plus.google.com/+DouglasCro...

Sometime I use Json to store data that view and edit by human. Cases like configuration files. It would be easier to communicate with people by commenting on the structure than writing a manual to explain.@irene

In some cases, no, or couldn't fit in a length of a sentence. Names could be ambiguous sometimes. @irene

Associate to it a json schema and you're good to go! This way you separate data from definitions.

It would be funny tho, serializing stuff with comments in it, I can already see it, when you call http://site.io/api you get a

{

// DONT USE IS BROKEN, SERIOUSLY DON'T USE THIS FIELD

"id": "1"

}

@irene yeah that's true which would be similar to an description attribute in xml.

And the answer is .... json5!!!

@json, please comment. 😉

Check out jsonc https://komkom.github.io/

I also like JSON.

For this reason, the domain name of my website uses the json series.
https://www.jsonformatting.com/

Fully agree, and that readability is exactly why a JSON file makes a perfectly fine little datastore for small stuff. That's the whole premise behind fjsondb — keep the format you already love, just add set/get/has/delete on top.