gura VS strictyaml

If one is looking for an alternative config format, the best designed I've seen is https://github.com/gura-conf/gura

I really like the Gura format (https://github.com/gura-conf/gura). Seems to combine the best of yaml, json, and toml for the use case of human created configuration files.

If we're on the topic of config languages, I'd like to plug Gura (https://github.com/gura-conf/gura). It's not too well-known, but it probably has the best design I've seen, and seems to have a good coverage of languages with an available library.

The first version of Serde Gura is now available! Gura is a simple and readable configuration language that will be familiar to any YAML and TOML user. Its essence lies in simplicity and was introduced in detail in this post on this subreddit.

Hi! I've just published a Gura parser written in pure Rust. (Repository link below!) Gura aims to offer a much simpler and more readable alternative to TOML and YAML. If you are familiar with the latter language, learning Gura is easy and intuitive.

Cool! There was a mistake and a very important section in README was deleted. We have added a Rationale section where we compare Gura with other languages, as explained there, Gura is not aimed to replace JSON as it's the faster configuration file in the world! But maybe can be able to take advantage of Gura's other benefits :D

Gura is a new configuration language readable as YAML, simple as TOML that supports variables, importing, and has standardized errors (official site | official repo).

NestedText already is the way I use YAML; everything is intepreted as a string. I have some trust in my YAML parser to not mangle most strings. I could use NestedText, but users would be unfamiliar with it, and IIRC the only parsers are in Python. But then I could use StrictYaml too https://github.com/crdoconnor/strictyaml

you can stick to a subset of YAML syntax (e.g. strictYAML)

YAML stands for "YAML Ain’t Markup Language" - this is known as a recursive acronym. YAML is often used for writing configuration files. It’s human readable, easy to understand and can be used with other programming languages. Although YAML is commonly used in many disciplines, it has received criticism on the amoutn of whitespace .yml files have, difficulty in editing, and complexity of the standard. Despite the criticism, properly using YAML ensures that you can reproduce the results of a project and makes sure that the virtual environment packages play nicely with system packages. (If you're looking for another way to share environments there are other alternatives to YAML which include StrictYAML (a type-safe YAML parser) and NestedText)

The example you linked provides this as an example of a YAML document that he wants his format to support.

That safe subset exists and is implemented in a number of languages. It is called strict-yaml: https://hitchdev.com/strictyaml/

StrictYAML\ (33 comments)

To me those are in the category of "nice to have", and the problem is that every developer has different preferences for these [1] [2]. But the main features of StrictYaml, like supporting comments and less syntactic noise, I think are pretty uncontroversial, and perhaps it's worth it to get people to switch over for those alone. It doesn't need to be perfect, it just needs to be a significant enough improvement over JSON, and I'd say those two features are more than enough

[1]: https://github.com/crdoconnor/strictyaml/issues/37

[2]: https://github.com/crdoconnor/strictyaml/issues/38