monolens VS nestedtext

I just cut a major release of Monolens, a declarative data language for transforming data.The new release comes with more documentation of various use cases (Kubernetes, seed files).* https://github.com/enspirit/monolens* https://github.com/enspirit/monolens/blob/master/documentation/1-introduction.md* https://github.com/enspirit/monolens/tree/master/documentation/use-cases/data-templates* https://github.com/enspirit/monolens/tree/master/documentation/use-cases/data-transformation

As /u/astatine said, an excellent but under-recognized alternative syntax for configuration files is NestedText, where everything is a string unless the ingesting code says otherwise, and there is no escaping needed ever.

I don't know what traits from markdown you'd hope for, but for a relatively obscure but technically excellent format, you can check out NestedText.

I recently came to appreciate and favor an alternative format called NestedText. Like YAML, indentation is used for structure, so like YAML, you may hate it.

I recently discovered NestedText, and really appreciate the design. To me, it hits the nail on the head where projects like strictyaml and hjson come very close.

I'm glad to see people experimenting with alternative document/object representations, but this one might be a hard sell: based on the README[1], it only has Python, Zig and Janet implementations so far. One of the nice things about YAML (and JSON, TOML, etc.) is that they have decently mature C, C++, or Rust libraries that other languages bind to.

[1]: https://github.com/KenKundert/nestedtext

NestedText

NestedText was left out. Has the feel of YaML, without all the complexity and user traps.