3 ms·
Fortunately we learned our lesson with YAML. (/s) Easier to write than JSON. But weirdly harder to get right in other ways, especially for nesting things. A
by BobbyTables2 1y ago
Fortunately we learned our lesson with YAML. (/s)
Easier to write than JSON.
But weirdly harder to get right in other ways, especially for nesting things.
Almost made the mistake of becoming simple to parse.
Alas, defeat was again snatched from the jaws of victory on that one…
- sandreas 1y agoTechnically YAML is a superset (or subset?) of JSON. https://yaml.org/spec/1.2-old/spec.html#id2759572 https://yaml.org/spec/1.2-old/spec.html#id2759572 However, I find the toml language somehow the better tech, while I still think that configuration should not be a "format" but a language. I think at least the recomposition of values with other values should be possible: CONFIG_PATH="$MAIN_PATH/config" And why would you configure: DEV_PATH="dev" PRD_PATH="prod" when you could do MAIN_PATH=env.IS_PROD ? "prod" : "dev"
- yencabulator 1y agoTOML with any kind of nested structure is an utter pain. It's only usable for the most trivial content.