Example · part of The finite reader
“GDPR means companies have to tell you what data they collect and let you delete it.” That sentence stands in for a long European privacy statute and thousands of pages of case law. It gets the central case right and the edges wrong: when the data must be deleted, who counts as a “controller” versus a “processor”, when ordinary consent is enough.
In a statute every clause has a set scope, and every “shall”, “may” and “subject to” does precise work a general reader cannot see. That is the full version, nearly closed to non-lawyers. The summary is the short version: the same trade as a powerful software tool and its easy wrapper. Legal language makes exact distinctions cheap for the trained and out of reach for everyone else, a built-in tilt.
Law is unusual, the book argues, in expecting both forms to coexist, with lawyers translating case by case. That puts preserving the full version and training its readers inside one profession. It also means getting the precision applied to your own situation costs money, the law’s version of what the book calls cost-shifting. The book marks this wealth gate as a darker pattern than its other examples.
Read the full argument
- Chapter 4: Optionality vs. Access, section “Legal codes”
- Chapter 4: Optionality vs. Access, section “What the curve is, and what it isn’t”
- Chapter 4: Optionality vs. Access, section “Where I’m still uncertain”
How it connects
- What it shows: Complex form, Compressed form, Cost of generality is accessibility, and vice versa, Cost-shifting from producers to consumers, Preservation vs. training (paired institutional functions)
- See also: Latin Mass vs. vernacular liturgy, matplotlib vs. seaborn
- Where the book discusses it: Chapter 4: Optionality vs. Access, Chapter 6: Where It All Gets Fucked Up, Chapter 10: Political Economy of Attention
← A Brief History of Time · The finite reader (9 of 14) · Complexity ceiling →
Explore all the ideas · Read the book in order · Open the interactive map