I really appreciate how this tackles the "key repetition" overhead in standard JSON without forcing a jump all the way to a binary format like Protobuf or MessagePack. It feels like a pragmatic sweet spot for high-volume data—especially in mobile or IoT contexts—where you want to optimize for bandwidth but still need the payload to be easily parsable and somewhat human-readable. It’s a clever way to bridge the gap between developer ergonomics and transfer efficiency.

looks like yaml with extra steps

- allows comments

- allows multiline strings

- no quotes around keys

this is just Lua tables

- no commas

now it's just s-expressions?

also JSON is already made for humans. I've seen a lot of people claim it isn't but I can't fathom that - it was literally created as a text-based format for humans to manually write in a text editor. If it were "made for machines" it would be bytecode.

I'm not saying this is bad but.. meh? Do we really need another bespoke JSON format that mostly does what Lua tables already do?