2.1 Why a config language has functions

Why does Nix use a purely functional language instead of YAML or JSON? This lesson answers the question every newcomer asks before starting a Nix language tutorial. Using a real Docker Compose file full of copy-pasted worker definitions, we show where YAML runs out of steam and how a config language with functions removes duplication for good.

In this video

• A Docker Compose file with six nearly identical workers, and why editing it safely is a minefield
• YAML anchors and merge snippets: how far the popular workaround gets you, and where the shallow merge quietly breaks down
• The same services rewritten in Nix, where one small function replaces all the copy-paste
• Rendering the Nix version to JSON with nix eval --json and inspecting it with jq
• One Nix document generating TOML, YAML and JSON: a single language for all your config formats

After this lesson

You can explain why Nix is a functional language and not just another YAML dialect, and you have seen the payoff that makes learning it worth your time. "