MOL (Markdown Object Language) is an alternative to JSON/XML, which is both more human friendly (very natural/easy to edit), and more LLM friendly (uses less tokens, LLMs like .md format already). It's basically a formal spec for parsing markdown-based config files, data files, etc. You can check it out at GitHub under mol-format/mol-specs. Supports JS/TS/.net/Rust currently with zero-dependency packages. Easy to implement in other languages. Maybe it's useful to other devs as well. Happy to hear feedback/criticism.
How does this compare to YAML and TOML? It feels that both of the above would be in the same bucket of "fewer tokens than JSON/XML and generally easier on the eye", with the benefit of having a pretty rich ecosystem already.
I'd be curious to hear about whether this has an edge when it comes to performance in any way, or whether it solves for a problem that other formats are missing the mark on.
MOL (Markdown Object Language) is an alternative to JSON/XML, which is both more human friendly (very natural/easy to edit), and more LLM friendly (uses less tokens, LLMs like .md format already). It's basically a formal spec for parsing markdown-based config files, data files, etc. You can check it out at GitHub under mol-format/mol-specs. Supports JS/TS/.net/Rust currently with zero-dependency packages. Easy to implement in other languages. Maybe it's useful to other devs as well. Happy to hear feedback/criticism.
How does this compare to YAML and TOML? It feels that both of the above would be in the same bucket of "fewer tokens than JSON/XML and generally easier on the eye", with the benefit of having a pretty rich ecosystem already.
I'd be curious to hear about whether this has an edge when it comes to performance in any way, or whether it solves for a problem that other formats are missing the mark on.