← Back to context Comment by silvestrov 8 hours ago Just say Norway to YAML. 12 comments silvestrov Reply merelysounds 8 hours ago This is a reference to YAML parsing the two letter ISO country code for Norway: country: no As equivalent to a boolean falsy value: country: false It is a relatively common source of problems. One solution is to escape the value: country: “no” More context: https://www.bram.us/2022/01/11/yaml-the-norway-problem/ Y-bar 8 hours ago We stopped having this problem over ten years ago when spec 1.1 was implemented. Why are people still harking on about it? merelysounds 4 hours ago A new spec version doesn’t mean we stop having the problem.E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml, a yaml subset.[1]: https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak... 2 replies → Etheryte 7 hours ago Because there's a metric ton of software out there that was built once upon a time and then that bit was never updated. I've seen this issue out in the wild across more industries than I can count. 3 replies → actionfromafar 7 hours ago Now add brackets and end-tags, I'll reconsider. ;) 1 reply → quotemstr 6 hours ago Because once a technology develops a reputation for having a problem it's practically impossible to rehabilitate it.
merelysounds 8 hours ago This is a reference to YAML parsing the two letter ISO country code for Norway: country: no As equivalent to a boolean falsy value: country: false It is a relatively common source of problems. One solution is to escape the value: country: “no” More context: https://www.bram.us/2022/01/11/yaml-the-norway-problem/ Y-bar 8 hours ago We stopped having this problem over ten years ago when spec 1.1 was implemented. Why are people still harking on about it? merelysounds 4 hours ago A new spec version doesn’t mean we stop having the problem.E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml, a yaml subset.[1]: https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak... 2 replies → Etheryte 7 hours ago Because there's a metric ton of software out there that was built once upon a time and then that bit was never updated. I've seen this issue out in the wild across more industries than I can count. 3 replies → actionfromafar 7 hours ago Now add brackets and end-tags, I'll reconsider. ;) 1 reply → quotemstr 6 hours ago Because once a technology develops a reputation for having a problem it's practically impossible to rehabilitate it.
Y-bar 8 hours ago We stopped having this problem over ten years ago when spec 1.1 was implemented. Why are people still harking on about it? merelysounds 4 hours ago A new spec version doesn’t mean we stop having the problem.E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml, a yaml subset.[1]: https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak... 2 replies → Etheryte 7 hours ago Because there's a metric ton of software out there that was built once upon a time and then that bit was never updated. I've seen this issue out in the wild across more industries than I can count. 3 replies → actionfromafar 7 hours ago Now add brackets and end-tags, I'll reconsider. ;) 1 reply → quotemstr 6 hours ago Because once a technology develops a reputation for having a problem it's practically impossible to rehabilitate it.
merelysounds 4 hours ago A new spec version doesn’t mean we stop having the problem.E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml, a yaml subset.[1]: https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak... 2 replies →
Etheryte 7 hours ago Because there's a metric ton of software out there that was built once upon a time and then that bit was never updated. I've seen this issue out in the wild across more industries than I can count. 3 replies →
quotemstr 6 hours ago Because once a technology develops a reputation for having a problem it's practically impossible to rehabilitate it.
This is a reference to YAML parsing the two letter ISO country code for Norway:
As equivalent to a boolean falsy value:
It is a relatively common source of problems. One solution is to escape the value:
More context: https://www.bram.us/2022/01/11/yaml-the-norway-problem/
We stopped having this problem over ten years ago when spec 1.1 was implemented. Why are people still harking on about it?
A new spec version doesn’t mean we stop having the problem.
E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml, a yaml subset.
[1]: https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak...
2 replies →
Because there's a metric ton of software out there that was built once upon a time and then that bit was never updated. I've seen this issue out in the wild across more industries than I can count.
3 replies →
Now add brackets and end-tags, I'll reconsider. ;)
1 reply →
Because once a technology develops a reputation for having a problem it's practically impossible to rehabilitate it.