Reinventing the wheel

[robertsynoradzki]

JSON + human readability + comments + smaller file sizes = YAML
Try it ;)

[apenwarr]

You forgot "+ turing complete". yaml goes way too far.

…

On Mon, Feb 3, 2020 at 10:20 AM roBsonn Null ***@***.***> wrote: JSON + human readability + comments + smaller file sizes = YAML Try it ;) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[jrencz]

https://json5.org also addresses the issues

[crawshaw]

I originally looked into json5. It suffers the usual fate of standard extensions, in that it adds more than is strictly necessary to solve the problem. Still, if it were widely used and had developed all the Go tooling I would expect of a widely used standard, I would have gone with it. But it doesn't, so it was easier to spend a couple days doing this.

Long-term, if the contents of our configuration files stabilizes and we are confident it won't change, we may come up a custom format to represent it.

[rogpeppe]

FWIW there's also https://github.com/rogpeppe/rjson.

[rogpeppe]

These days, I'm actually a fan of Cue's syntax. If you use a strictly concrete subset, I think that could make a great JSON-alternative. I think it could be worth doing that as a standalone thing.

[frioux]

I'm excited to use this; a simple config format that I already know the semantics of with a few basic improvements. ++

[NuSkooler]

Or HJSON which already covers this and has the name...

[bradfitz]

HSON goes too far, IMO. YAML also went that path where they just kept adding stuff.

tailscale/hujson is JSON + comments. Not multiline strings, omitting commas, omitting quotes, etc. At a certain point it gets hard to even recognize it as JSON.

[FyiurAmron]

obligatory xkcd: https://xkcd.com/927/