json5

Hadn't heard of JSONC, but I've always been a proponent of JSON5 for this reason. https://github.com/json5/json5

Is the list on their website not good? https://github.com/json5/json5/wiki/In-the-Wild And it shouldn't take much to modify an existing JSON parser.

I believe that's JSON5. https://github.com/json5/json5 It's my preferred configuration file format, it fixes all the problems I have with JSON (trailing commas, comments) without turning it into a mess full of gotchas like YAML.

I can relate. But after using JSON for a while (in files that I edit by hand), I found that I really want comments and trailing commas (which leads to https://nigeltao.github.io/blog/2021/json-with-commas-commen...). Next I'd probably want multiline strings (leading to https://github.com/json5/json5). But if you use those extensions, all your tooling breaks. (Aside: I think the real bike-shedding would start when you want to add some syntax for raw string literals, e.g. heredocs; it's one of those features that feels redundant, until the day when you really need it and you can't bear the pain of repeatedly escaping and unescaping.)

The reactions were to the https://github.com/json5/json5/tree/v0.0.0 version I think. Later versions (including what we see today on the repository) acknowledged much of the critique and narrowed down the scope to human writeable. It might seem like unwarranted "nerd fury" from the perspective of what JSON5 has become, but at the time it was presented as (and naively believed to be) a better JSON in every way. Apparently the seeming "fury" was actually productive input.

Apologies for the, in retrospect, somewhat lazy posting of an article with no comment. I thought that article had a section about how many of them allow single quotes if you don't "enable strict." I am not seeing it on review, though; so either I made that up in my mind, or I'm remembering another article. Either way, apologies. I did find https://github.com/json5/json5 no a quick search that basically says what I asserted about people just jumping to another standard for things that you hand write. I was probably also thinking heavily about python's dict syntax. (And I confess, I still don't know when to use single versus double quotes in python...)

Also, there is JSON5, which I think is more widely known https://json5.org https://github.com/json5/json5

See also: https://json5.org https://github.com/json5/json5

Cool! JSON5 looks intriguing. The core project implements a JavaScript module [1] but it looks like there are also experimental JSON5 libraries for Go [2], Python [3], Ruby [4], and Rust [5]. [1]: https://www.npmjs.com/package/json5 [2]: https://github.com/yosuke-furukawa/json5 [3]: https://pypi.org/project/json5/ [4]: https://github.com/bartoszkopinski/json5 [5]: https://docs.rs/json5/ I noticed that JSON5 doesn’t include a Date type. There have been discussions about this in both the JavaScript [6] and spec [7] repos but with no resolution yet. [6]: https://github.com/json5/json5/issues/3 [7]: https://github.com/json5/json5-spec/issues/4

In a different realm, there are people that find even ol' JSON annoyingly strict, and we prefer to just grab JSON5 instead (https://github.com/json5/json5) at least for system-local configs. ..there was a wise saying about how you gotta "stop worrying and love the bomb" ;)

> It would force the consumer of that data to replicate the environment. It won't, because JSON is a standard. Imperfect like all standards but practically good enough. And "plain text" just means "an undefined syntax that I have to mostly guess". And nobody "programs" in bash or awk anymore. The "standard scripting languages" for all sane devs are Python or Ruby (and some Perl legacy) and parsing JSON in them is trivial. The "UNIX philosophy" was a cancerous bad idea anyway and now it's thankfully being eaten alive by its own children, so time to... rejoice?! EDIT+: Also, if I feel truly lazy/evil (like in "something I'll only in this JS project"), I would use something much much less standard than JSON, like JSON-5 (https://github.com/json5/json5), which will practically truly force all consumers to use JS :P

is this a stab at json5? https://github.com/aseemk/json5