I'd like to write comments in my .json files and not have GitHub's syntax highlighter go nuts with red error underlines.

When I searched for human-readable JSON options, I also found jsonc and Hjson. Are these efforts all essentially equivalent? If so should we merge these fragmented camps and make a de facto standard? Even better, what's involved to evolve the actual IETF standard?

The JSON parser that we use already supports comments just fine, but people keep complaining that (1) it's not "standard" (i.e. the world's worst parser JSON.parse() doesn't support it) and (2) that various syntax highlighters reject it.

I'm happy to rename thousands of file extensions and release major breaking versions of our tools... but I'm unsure which way to go:

1. Rename everything to .json5
2. Rename everything to .jsonc
3. Keep .json and go pester the various tools to accept comments, because even the inventor of JSON said he was cool with comments

Also, maybe someone should update the Wikipedia article to talk about these community efforts.