Switch to NestedText?

[mourner]

I just stumbled upon a very similar initiative — https://nestedtext.org, but instead of adopting a strict YAML subset, it goes even further, lightly breaking compatibility with YAML in favor of an even simpler syntax & spec. I think switching this project to NestedText format (and maybe renaming accordingly) is definitely worth considering. Advantages:

• Adopting an existing format instead of inventing our own which is subtly different.
• We can reuse the test suite, which seems very reasonable and compact (trying to figure out which subset of official YAML test suite to use was a nightmare).
• Simpler means better! And it still covers the use cases I have in mind perfectly (simple configs & static pages front matter).

Thanks @KenKundert @kalekundert for such a nice project!

[kalekundert]

We're really interested in getting NestedText implementations for languages other than python, so if you're thinking about writing one for javascript, we'd be happy to help in any way we can (e.g. if you find any ambiguities we overlooked, or have issues with the test suite, etc).

[KenKundert]

And we would be happy to feature your project on the nestedtext.org website.

[mourner]

Great! I started experimenting with a proof of concept parser and so far I love how unambiguous it is — each line can be quickly categorized when tokenizing, making parsing very simple, fast and easy to reason about.