json5 VS kdl

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.

JSON5 support

Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.

I think JSON5 is fairly close to this: https://json5.org

I reckon the only thing it's missing to be truly accessible to non-techies is that string values still need to be quoted, i.e. you can't have:

key: this is my value

(I'm definitely not saying it would be a good idea to allow quotes to be dropped, just that that's the only potential stumbling block I see for non-techies.)

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.

Might be interesting to check out json5.

https://json5.org/

I can relate. But after using JSON for a while (in files that I edit by hand), I realised that I really wanted 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.

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 can't bear the pain of escaping.

IMO, there’s a wide unexplored design space between the minimalism of Lisp and richness of other languages. A programming language inspired by something like KDL (https://github.com/kdl-org/kdl) has the potential to be in a very sweet spot between the two. "Everything is a node" instead of "everything is a list" is only slightly more complicated, but also vastly more readable that a soup of parenthesis.

KDL is a variant of SDLang that’s worth checking out.

https://github.com/kdl-org/kdl

Here's an example of how a HTML page would be presented.

https://github.com/kdl-org/kdl/blob/main/examples/website.kd...

I'd love to understand why all the advertised implementations have permissive licenses except for the Rust implementation, which is released under the Parity Public License 7.0.0 [1]? This seems to be as restrictive as the GPL, no?

In my mind, copyleft licenses applied to infrastructural projects like kdl-rs prematurely limits their adoption and promotes the development of alternatives with more permissive licensing, since the spec is released under a Creative Commons license [2].

[1]: https://github.com/kdl-org/kdl-rs/blob/87f836134c1d901ff5ce6...

[2]: https://github.com/kdl-org/kdl/blob/785abebfc507ff6b7bdeac07...

It does have a schema language, and a query language. There's no translation language (yet?) but if that's of interest, that sounds like a thing to bring up on github!

p.s. if anyone is interested in helping or just wants the info, this is the tracking issue for implementations supporting 1.0 (the actual thing that just got released): https://github.com/kdl-org/kdl/issues/144

There's an issue for this~ https://github.com/kdl-org/kdl/issues/54

Why no XLang implementation? You haven't written it yet, of course! What was just stabilized was the KDL specification. There are a number of supported impls, but one challenge they were having was targeting a moving target. So we wrapped everything up to make it easier to write new ones! Please file an issue if your favorite language is missing!

Oh nice. It will be a nice library to use to parse KDL (https://github.com/kdl-org/kdl)

It's still in its infancy but I'm keeping an eye on kdl