<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l" -->

---
title: It's not the YAML spec's fault, but | daily.dev
description: A deep dive into the origin of YAML's notorious implicit typing issues, including the infamous 'Norway Problem' where unquoted 'no' gets parsed as a boolean....
canonical: https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: It's not the YAML spec's fault, but | daily.dev
og:description: A deep dive into the origin of YAML's notorious implicit typing issues, including the infamous 'Norway Problem' where unquoted 'no' gets parsed as a boolean....
og:url: https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l
og:image: https://api.daily.dev/og/posts/vTObT282l.png
og:image:alt: It's not the YAML spec's fault, but
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# It's not the YAML spec's fault, but

**[Lobsters](https://daily.dev/sources/lobsters)** · 25 min read · 0 upvotes · 0 comments

## Summary

A deep dive into the origin of YAML's notorious implicit typing issues, including the infamous 'Norway Problem' where unquoted 'no' gets parsed as a boolean. By digging through the original YAML spec revisions (1.0, 1.1, 1.2) and scraping thousands of emails from the early-2000s yaml-core mailing list, the author finds that the spec authors always intended libraries to default to treating scalars as strings, with implicit typing being optional and application-specific. The real failure was a lack of oversight: library authors, especially Ruby's Syck (accepted into Ruby's standard library in 2003) and Python's PyYAML, never implemented this string-first recommendation, cementing broken implicit-typing behavior as the de facto standard for millions of developers regardless of what the spec said. The author argues the spec itself isn't to blame, but the ecosystem of implementations that diverged from its intent is.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://slugcat.systems/post/26-09-10-yaml-spec>

## Questions this post answers

### why does YAML parse the word 'no' as a boolean instead of a string, and is that mandated by the spec

It is not mandated by the spec. Mailing list archives from the yaml-core project show the original spec authors intended YAML libraries to default to treating scalars as strings, with implicit typing (like recognizing 'no' as a boolean) being optional and application-specific. The behavior became standard because Ruby's Syck library, accepted into Ruby's standard library in August 2003, implemented broken implicit typing and was never fixed, cementing that behavior for users despite the spec's actual recommendation.

_Debugging YAML config quirks gets easier when daily.dev surfaces deep dives like the reasoning behind the Norway Problem._

### does the YAML 1.2 spec still support base 60 numbers and yes/no booleans

No, YAML 1.2's Core Schema, introduced roughly five years after YAML 1.0, removed sexagesimal (base 60) numbers and yes/no style booleans, defining a more restrained default type-resolution schema built on top of JSON schema. However, widely used libraries such as PyYAML still do not support the YAML 1.2 Core Schema even though it is the officially recommended default.

_daily.dev helps developers track gaps between a spec's recommendations and what libraries actually implement._

## Community take

How the wider developer community reacted, aggregated from 1 discussion and 19 comments across lobsters (as of 2026-09-11).

**TL;DR:** Despite the post's argument that library authors are to blame, many commenters push back and insist the YAML spec itself is at fault, while a side-thread riffs on how XML and other formats were historically shoehorned into everything via hype cycles.

**Sentiment:** 10% positive · 25% mixed · 65% skeptical

**The case for**

- A few people appreciate that the author actually went through the trouble of scouring old mailing-list archives.
- Some argue YAML remains preferable to hand-editing JSON for certain devops use cases.

**The pushback**

- Multiple commenters flatly reject the post's central claim and insist the spec itself is to blame.
- Some feel YAML is misused for tasks (like CI pipeline configs) that should really be actual code.
- One commenter calls out perceived hypocrisy in the post criticizing 'falsehoods' while itself repeating a marketing tagline about YAML being 'human-friendly.'
- Someone suggests actually trying to write a parser for YAML would change one's opinion of it.

**By community**

- lobsters (skeptical): Top comments largely reject the post's thesis and insist the spec itself is to blame, with a long tangent about XML and format hype cycles.

**Hottest debate:** Whether the YAML spec itself is at fault versus the post's claim that implementation divergence is to blame.

**Open questions**

- Was there any historical discussion about restricting map keys to identifier-like syntax instead of allowing arbitrary unquoted strings?

**Highlights**

> It was, in fact, the YAML spec's fault.
> — [max-headroom on lobsters · 28 points, 3 comments](https://lobste.rs/s/bsvc7a/it_s_not_yaml_spec_s_fault#c_dticiz)

> It is 100% the yaml specs fault.
> — [zaphar on lobsters · 8 points](https://lobste.rs/s/bsvc7a/it_s_not_yaml_spec_s_fault#c_vqlxvo)

> The blog post starts out with (emphasis mine) > the author proudly repeats *while posting falsehoods* ... Then has this line/quote: > YAML™ (rhymes with “camel”) is a *human-friendly, * ... Pot, Kettle, fucking black? The objectively true and undeniable expansion of the YAML acronym is Yet-Another-Migraine-Looming. It's human friendly in the sense that razor wire is human friendly: you won't be harmed if you don't fucking touch it, and will absolutely work as an effective way to keep other people away from you.
> — [stephenr on lobsters · 1 points, 1 comments](https://lobste.rs/s/bsvc7a/it_s_not_yaml_spec_s_fault#c_k2pj2j)

> The worst is when YAML is used for something that should be actual code (looking at GitHub Actions, GitLab CI, Azure Pipelines...). That aside, what would you suggest for human-writable data? JSON lacks comments and TOML really falls apart for complex data. And I've seen enough bespoke formats from hell that I'd much rather jump to literally anything with a concrete spec.
> — [camblomquist on lobsters · 1 points](https://lobste.rs/s/bsvc7a/it_s_not_yaml_spec_s_fault#c_sj1hrh)

> Good job actually scouring the emails. > They wanted unquoted strings Unquoted strings don't seem that valuable to me – except for map keys, which typically act as identifiers (and often map to identifiers in programming languages, which have restrictions placed upon their form) and therefore tend to be short, free of whitespace, and limited in character set. It would be interesting to see if there was discussion about not allowing unquoted strings, or on map keys being restricted to "identifiers" instead of arbitrary values.
> — [mira on lobsters · 1 points](https://lobste.rs/s/bsvc7a/it_s_not_yaml_spec_s_fault#c_kevtsl)

**Source threads**

- [lobsters](https://lobste.rs/s/bsvc7a/it_s_not_yaml_spec_s_fault) · 39 points · 19 comments

## Similar posts on daily.dev

- [YAML? That’s Norway problem](https://daily.dev/posts/yaml-that-s-norway-problem-jgyckvk2a) · Programming Digest · 4 upvotes · 0 comments
- [Ruby May Finally Fix the Famous “Norway Problem”](https://daily.dev/posts/ruby-may-finally-fix-the-famous-norway-problem--hkkhy7rxd) · RUBYLAND · 2 upvotes · 0 comments
- [In Defense of YAML](https://daily.dev/posts/in-defense-of-yaml-0iiadtzpt) · Lobsters · 0 upvotes · 0 comments
- [YAML: The Language That Quietly Runs Modern DevOps](https://daily.dev/posts/yaml-the-language-that-quietly-runs-modern-devops-ojznade2q) · Medium · 1 upvotes · 0 comments

---

[View this post on daily.dev](https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"It's not the YAML spec's fault, but","url":"https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l"},"datePublished":"2026-09-11T01:40:34.672Z","dateModified":"2026-09-11T14:56:27.380Z","description":"A deep dive into the origin of YAML's notorious implicit typing issues, including the infamous 'Norway Problem' where unquoted 'no' gets parsed as a boolean....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f6ea51d46dd9b099710d9773c6bdf3b2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f6ea51d46dd9b099710d9773c6bdf3b2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"","timeRequired":"PT25M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"It's not the YAML spec's fault, but"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/it-s-not-the-yaml-spec-s-fault-but-vtobt282l#faq","mainEntity":[{"@type":"Question","name":"why does YAML parse the word 'no' as a boolean instead of a string, and is that mandated by the spec","acceptedAnswer":{"@type":"Answer","text":"It is not mandated by the spec. Mailing list archives from the yaml-core project show the original spec authors intended YAML libraries to default to treating scalars as strings, with implicit typing (like recognizing 'no' as a boolean) being optional and application-specific. The behavior became standard because Ruby's Syck library, accepted into Ruby's standard library in August 2003, implemented broken implicit typing and was never fixed, cementing that behavior for users despite the spec's actual recommendation. Debugging YAML config quirks gets easier when daily.dev surfaces deep dives like the reasoning behind the Norway Problem."}},{"@type":"Question","name":"does the YAML 1.2 spec still support base 60 numbers and yes/no booleans","acceptedAnswer":{"@type":"Answer","text":"No, YAML 1.2's Core Schema, introduced roughly five years after YAML 1.0, removed sexagesimal (base 60) numbers and yes/no style booleans, defining a more restrained default type-resolution schema built on top of JSON schema. However, widely used libraries such as PyYAML still do not support the YAML 1.2 Core Schema even though it is the officially recommended default. daily.dev helps developers track gaps between a spec's recommendations and what libraries actually implement."}}]}
```

