The JSON Empire: How a Minimal Data Format Took Over the Internet

Scope and framing. JSON is not a company or a product but an open data-interchange syntax and file format. Its common filename extension is .json, its IETF media type is application/json, and its value model is intentionally tiny: objects, arrays, strings, numbers, true, false, and null. That minimalism later became the basis of its global spread. If we ask who “founded” JSON, the most accurate answer is not “a sole inventor,” but rather that Douglas Crockford was the key namer, describer, standardizer, and evangelist of JSON. Crockford himself explicitly said he did not “invent” JSON; he said he “discovered” it, and noted that developers had already been using JavaScript literals for data transport before his 2001 discovery. In that sense, his historic contribution was to turn a scattered technique into a named, documented, shareable, standardizable public format. As for his parents, exact birth year, exact birthplace, and family class background, reliable public information remains limited.

Background and education. Crockford’s biographical record is much thinner than his technical record. What can be verified is that he is repeatedly framed as a product of the public education system, and external interviews describe him as having grown up in Southern California. His formal degree came from San Francisco State University, where he studied Radio and Television from 1971 to 1975. While in school, he supported himself by doing computer consulting for university departments, and he later started but did not publicly document the completion of a master’s program in Educational Technology. His path into programming was famously indirect: according to Coders at Work, he took a Fortran course after he could not get studio time for his broadcasting major. That matters because it helps explain why he never approached computing only as an abstract language theorist; he approached it as a systems-and-media builder. Interviews and profiles consistently portray him as a simplifier, a critic of unnecessary complexity, and someone who believed programmers should know the history of computer science.

Career path and project network. Crockford’s early work started outside the Web. In 1976 he was a research assistant at SRI International; from 1977 to 1982 he worked at Basic/Four on utilities, word processing, compiler optimization, and office automation. From 1982 to 1984 he was at Atari, where he worked on games, development tools, graphics, and music systems. From 1984 to 1992 he was at Lucasfilm, where he dealt with digital entertainment systems, interactive media, Nintendo cartridges, CD-ROM games, and early online community work. In 1992 he became Director of New Media at Paramount. His entrepreneurial phase then deepened: at Electric Communities / Communities.com, he held multiple founder-level roles and, by his own account, helped build a globally scalable distributed platform that raised $40 million in venture capital. Then came State Software in 2001–2002, where he served as founder and CTO and where he says he discovered JSON. After a consulting-and-research period under Faceless Corporation, he became a Distinguished Architect at Yahoo! and then PayPal, before shifting in 2019 to Virgule-Solidus, where he continues as founder and publisher. Across this journey, the most important recurring collaborators and institutions included Randy Farmer, Chip Morningstar, Yahoo, PayPal, O’Reilly, Ecma TC39, and Tim Bray at the IETF.

The birth of JSON and its standardization. JSON emerged from a very practical engineering problem. At State Software, Crockford and collaborators needed to send messages back and forth between browsers and servers. In the Computer History Museum oral history, Chip Morningstar recalled that they realized the browser could simply understand a JavaScript object literal if they sent data in that form. At the same time, customers kept pushing for XML, which they regarded as too complicated for the browser-centered problem they were solving. So they named the format JavaScript Object Notation, registered json.org, published a short syntax page, and effectively used documentation and naming to make the format socially legible before it was formally standardized. The timeline is straightforward: discovery in 2001, json.org in 2002, RFC 4627 in 2006, built-in JavaScript support with ECMAScript 5 in 2009, ECMA-404 in 2013, RFC 7159 in 2014, I-JSON RFC 7493 in 2015, and RFC 8259 plus alignment with ECMA and ISO in 2017. Design-wise, JSON won by being radically narrow: it was defined as a lightweight, text-based, language-independent syntax. It intentionally defined syntax, not semantics. That same minimalism is also the source of its technical limitations: no direct support for cyclic graphs, poor suitability for binary data, duplicate-key ambiguity, security risks when parsed with eval, and a need for UTF-8 in open ecosystems. The later emergence of I-JSON, JSON Schema, and OpenAPI shows that JSON’s long-term role was to act as a thin universal substrate, with richer constraints added by other layers.

Assets, monetization, and living legacy. Crockford’s most important associated brands and assets include json.org, JSLint, JSMin, crockford.com, Virgule-Solidus, the JSON reference implementations, and his books such as JavaScript: The Good Parts and How JavaScript Works. Some of these are closer to real economic assets, such as his publishing vehicle and book copyrights. Others are better understood as influence assets: the authority of json.org, authorship of RFC 4627, tool reputation, and his role as a JavaScript public intellectual. His business model evolved across salaried technical work, venture-backed startups, consulting, expert-witness work, platform architect roles, book publishing, and speaking. JSON itself was never primarily a direct revenue engine; it was an influence engine that converted into career capital. The format’s present-day footprint is enormous and concrete. OpenAPI says an OpenAPI document is itself a JSON object; npm requires package.json for published packages; GitHub REST recommends JSON media types; Kubernetes defaults to JSON for API message bodies; Stripe returns JSON-encoded responses; the Library of Congress exposes JSON/YAML APIs; and JSON Schema has grown into a large validation and interoperability ecosystem. That is why Crockford’s influence persists even outside any single company role: JSON remains embedded in the daily machinery of software.

Criticism, controversy, and present standing. Crockford’s longest-running controversy centered on licensing, not on JSON’s syntax itself. The JSON.org license included the famous clause that the software must be used for “Good, not Evil,” which made it unacceptable to organizations such as the FSF and outside the OSI conception of open-source-compliant licensing. Only in 2022 did the JSON-java release switch to the public domain, easing that friction. Technical criticism of JSON has been equally persistent: developers complain about the lack of comments, duplicate-key ambiguity, number-precision hazards, missing built-in semantics for dates and binary data, and its awkwardness for hand-edited configuration. Crockford later explained that comments were removed because they were being used for parsing directives, which would have harmed interoperability. His wider public reputation follows the same pattern: high contribution, high conviction, and a steady willingness to oppose complexity. He was a prominent critic of the ES4 direction and favored the more restrained ES3.1/ES5 path, which later largely prevailed. Today, the verifiable public record still shows him active through Virgule-Solidus, his personal site, public code repositories, and speaking profiles. The cleanest historical judgment is this: Crockford’s most important contribution was not merely to create a convenient format, but to name, explain, publish, standardize, and socially legitimize a data notation that became the default common language of networked software. Open questions remain around the finer details of his private family background and exact birth data, but not around his historical place in the architecture of the modern Web.