I honestly still cant believe they actually updated the spec to allow comments but we really did it and configuration files everywhere are going to be so much easier to read now. It felt like shouting into the void for a while there so thank you for sticking with this …
January 21, 2013
Final supporters
Use-case: Validation of configuration files done in JSON with comments should succeed, but currently does not.
Why: Since JSON is frequently used for configuration files, as distinguished from bulk data transport, allowing comments in JSON will greatly ease development and configuration tasks. Additionally, securely stripping out comments when required is not a difficult task and is supported by many tools.
Updates
July 1, 2012
I was just looking at a massive stack of config files and honestly the sheer amount of frustration people have with this spec is wild. Someone sent me a message about how their entire build pipeline crashed because of a trailing comment and I just thought yes exactly that is why this needs to change.
14 Comments
I would be happy if the MAY became SHOULD in "A JSON decoder MAY accept and ignore comments". (https://groups.yahoo.com/neo/groups/json/conversations/topics/152)
its 2016 and we are still arguing about human readable comments? come on.
Honestly having to use a separate pre-processor just to keep notes in a config file is a pain. JSON is standard for configs now so just update the spec.
I end up using json5 anyway because standard json is too restrictive for my dev team. Would be nice if the base spec caught up with how people actually write code.
WHY IS THIS SO HARD. Just add it already.
Comments = whitespace.
Without comments, json config files are pretty unworkable.
Share this petition
Share this petition to help it reach more people.
Your share link
I honestly still cant believe they actually updated the spec to allow comments but we really did it and configuration files everywhere are going to be so much easier to read now. It felt like shouting into the void for a while there so thank you for sticking with this …
January 21, 2013
Final supporters
Use-case: Validation of configuration files done in JSON with comments should succeed, but currently does not.
Why: Since JSON is frequently used for configuration files, as distinguished from bulk data transport, allowing comments in JSON will greatly ease development and configuration tasks. Additionally, securely stripping out comments when required is not a difficult task and is supported by many tools.
Updates
July 1, 2012
I was just looking at a massive stack of config files and honestly the sheer amount of frustration people have with this spec is wild. Someone sent me a message about how their entire build pipeline crashed because of a trailing comment and I just thought yes exactly that is why this needs to change.
14 Comments
Funny that the main reason the author of JSON wanted to get rid of comments was because people might abuse them by adding annotations etc.. Yet the solution is to simply demand comments get stripped and discarded.
I would be happy if the MAY became SHOULD in "A JSON decoder MAY accept and ignore comments". (https://groups.yahoo.com/neo/groups/json/conversations/topics/152)
its 2016 and we are still arguing about human readable comments? come on.
Honestly having to use a separate pre-processor just to keep notes in a config file is a pain. JSON is standard for configs now so just update the spec.
I end up using json5 anyway because standard json is too restrictive for my dev team. Would be nice if the base spec caught up with how people actually write code.
WHY IS THIS SO HARD. Just add it already.
Comments = whitespace.
Without comments, json config files are pretty unworkable.
Share this petition
Share this petition to help it reach more people.
Your share link
Petitions like this
Other petitions you might want to support
Scan to share
Anyone who scans this can sign the petition.
Funny that the main reason the author of JSON wanted to get rid of comments was because people might abuse them by adding annotations etc.. Yet the solution is to simply demand comments get stripped and discarded.