I met Daniel (creator of KSON) a while ago and have helped out with a few things, working towards this first beta release. I don't want to hijack the comments section, but there's an article I just finished writing that might shed a bit of context into why KSON exists. It's called "Configuration files are user interfaces" (see https://ochagavia.nl/blog/configuration-files-are-user-inter...). Hope it helps folks understand where KSON is coming from!
So incredibly excited for this to come out! What an improvement in the quality of life for developers! My hunch is that this will also come in handy when sending data into LLMs, being able to reduce input tokens without losing fidelity is becoming an ever more important ordeal.
Nice to see this out there! Been playing with the token efficiency, looks like around 10% savings vs regular JSON/YAML. Not massive but it adds up. The embedded code thing is cool. Tired of configs that need weird templating or scripts all over the place just to do basic logic. Will check this out on some projects.
What about manipulating the data?
Does it support embedded comments, like TOML does? What happens if you round-trip that through JSON? What about the other superset features?
What does KSON stand for?
There's a lot said about JSON and YAML on the main page, but why is this better than TOML?