JSON Schema Demystified: Dialects, Vocabularies and Metaschemas

JSON Schema—the rulebook for checking if your app’s data looks right—just got a plain-English explainer, and devs are cheering and jeering. The post promises to decode scary words like “metaschema,” “dialects,” and “vocabularies,” and shows how schemas are rules written in JSON (a popular text format for data) that can even validate themselves via a metaschema. But the comments? Pure theater. Some readers say the terminology is a power move to make normals feel dumb; others love the nerdy recursion. One standout meme: typo police catching “stirng” with spec-backed swagger.

Hot takes are flying. Adamzwasserman drops philosophy—“stop lying about where truth lives”—arguing tools should stop duplicating state. Afiori grumbles everyone’s stuck on ancient Draft 4 while the spec keeps marching. Boricj calls JSON Schema “too flexible,” great to write but painful to build tools around. Jopsen misses the simple days, claiming validators now feel like boss fights. Jhoechtl says the spec made an “open world” mistake; most teams just want strict rules: this message or bust. The vibe: half of devs want fewer buzzwords and a lock-tight rulebook, half want the flexibility and power. And everyone agrees: the lingo could chill.