YAML? That's Norway Problem
lab174.com
YAML? That's Norway Problem
1–10 of 46 posts
Re: YAML? That's Norway Problem
#2For yaml in the context of Ansible, this was recently fixed a little while back in v2.19.
They got more strict about booleans. For those who need/want the old behavior, ALLOW_BROKEN_CONDITIONALS can be set in the ansible.cfg or `is truthy` can be used for python-like version, but it becomes explicit vs being implied.
Re: YAML? That's Norway Problem
#3Was backward compatibility the main reason YAML kept these implicit conversions for so long, or was there a stronger usability argument originally?
Re: YAML? That's Norway Problem
#4YAML is the worst format.
You are literally one missing tab away from breaking your entire configuration file. Yet the industry keeps pushing it for the sake of “simplicity” - for small configurations sure, it’s fine, but many hundred lines of config entries? Good luck fixing it, if something goes wrong.
I still can’t get why software engineers suddenly started to hate XML.
Re: YAML? That's Norway Problem
#5YAML is the worst format. You are literally one missing tab away from breaking your entire configuration file. Yet the industry keeps pushing it for the sake of “simplicity” - for small configurations sure, it’s fine, but many hundred lines of config entries? Good luck fixing it, if something goes wrong. I still can’t get why software engineers suddenly started to hate XML.
Re: YAML? That's Norway Problem
#6YAML is the worst format. You are literally one missing tab away from breaking your entire configuration file. Yet the industry keeps pushing it for the sake of “simplicity” - for small configurations sure, it’s fine, but many hundred lines of config entries? Good luck fixing it, if something goes wrong. I still can’t get why software engineers suddenly started to hate XML.
Long time ago i thought .properties was bad, as it has no structure. But later I realized repeating full path to every config param is really good for readability, and code reviews.
The only thing I wish it had is @import-s from a separate files, that way we could split local/checkedin configs. YAML doesn't have @imports as well (only rudimentary from the same file), I have only seen them at HOCON.
Re: YAML? That's Norway Problem
#7YAML is the worst format. You are literally one missing tab away from breaking your entire configuration file. Yet the industry keeps pushing it for the sake of “simplicity” - for small configurations sure, it’s fine, but many hundred lines of config entries? Good luck fixing it, if something goes wrong. I still can’t get why software engineers suddenly started to hate XML.
Cause it's very verbose. A lot more syntax to break.
I personally think the best is one of the humanized json ones like https://maml.dev/
Re: YAML? That's Norway Problem
#8YAML is the worst format. You are literally one missing tab away from breaking your entire configuration file. Yet the industry keeps pushing it for the sake of “simplicity” - for small configurations sure, it’s fine, but many hundred lines of config entries? Good luck fixing it, if something goes wrong. I still can’t get why software engineers suddenly started to hate XML.
Cause it's very verbose. A lot more syntax to break. I personally think the best is one of the humanized json ones like https://maml.dev/
It wouldn't need to be if closing tags were allowed to be unnamed. For most cases, we can tell the closing tags easily enough for simpler files:
MAML
minimal
readable
1
Anton Medvedev
JSON
2001
MAML
2025
This is a multiline raw strings.
Keeps formatting as-is.
Re: YAML? That's Norway Problem
#9Really? Putting quotes around strings is called escaping now?
One workaround is to escape the string, like this:
countries:
- DE
- FR
- "NO"
- PL
- RO
Re: YAML? That's Norway Problem
#10[dead]