2 ms·
>basically YAML, "but better" That was my intention behind this, too: https://github.com/crdoconnor/strictyaml/ https://github.com/crdoconnor/strictyaml/ The
by pydry 6y ago
>basically YAML, "but better"
That was my intention behind this, too:
https://github.com/crdoconnor/strictyaml/ https://github.com/crdoconnor/strictyaml/
The general structure of YAML is fine I think but its feature set grew a little bit out of control.
The "cleanliness" of the format leads to one of its inherent weaknesses - syntax can't be used to encode type information so you either need a schema to encode type information (strictyaml approach) or have magic conversions (yaml approach) or to assume strings (strictyaml w/o schema/nestedtext).
The interesting thing I discovered about schemas building this is that it kind of pays to make them extensible and build them in a turing complete language. Schema validation done using a non-turing complete language (e.g. jsonschema) allows for cross language usage but it ends up being a kind of blunt object.