JSON

Douglas Crockford was working at State Software and looking for a simple way to enable communication between a server and a web browser. He noticed that JavaScript had a convenient syntax for representing objects: key-value pairs within braces. The idea came to him to extract this notation from the language and turn it into a standalone data exchange format.

In 2001, Crockford formalized this subset of JavaScript under the name JSON, for JavaScript Object Notation. He published the specification on json.org and provided implementations in several languages. The format consisted of just a few rules: six data types were sufficient (strings, numbers, booleans, arrays, objects, and the null value) to represent complex structures. This brutal simplicity contrasted with the verbosity of XML, which was ubiquitous in data exchange at the time.

Official standardization came in 2006 with IETF RFC 4627. The document established the MIME type application/json and defined the precise syntax. Other versions followed: RFC 7158 in 2013, RFC 7159 in 2014, and RFC 8259 in 2017. Each revision clarified technical points and adjusted the specification to meet emerging needs in the field.

JSON became dominant because it addressed concrete needs. Its minimalist syntax remained human-readable while being easy for machines to parse. The absence of tags reduced the size of exchanged messages. And most importantly, it naturally meshed with JavaScript, the language that already dominated client-side web development. Developers had nothing new to learn because they were using structures they manipulated daily.

The web giants adopted it one after another. Yahoo! was among the first to integrate it into its services, followed by Google, Facebook, and Twitter. This massive adoption transformed JSON into a de facto standard for web APIs. REST architectures, which were becoming the norm for designing web services, aligned perfectly with this lightweight format.

The ecosystem around JSON developed at an astonishing pace. Libraries appeared in all major languages. Specialized variants emerged: GeoJSON for geographic data, JSON Schema for validating document structure. NoSQL databases like MongoDB or CouchDB adopted it as their native storage format, extending its influence beyond simple data transport.

Modern JavaScript frameworks like Angular or React manipulated JSON natively. Mobile development leveraged its lightweight nature to conserve bandwidth. JSON gradually became an invisible but ubiquitous component of web infrastructure, present in nearly every exchange between applications.

This simplicity also revealed its limitations. The inability to add comments hindered documentation. Number representation raised precision questions related to floating-point calculations. The absence of a standard format for dates forced developers to establish their own conventions. Variants like JSON5 or JSONC appeared to fill these gaps, at the risk of fragmenting the ecosystem.

A recent analysis of public JSON files shows that developers intensively exploit the format’s capacity to represent nested structures. Objects contained in arrays themselves nested within other objects have become commonplace. This flexibility allows great expressiveness while maintaining a certain regularity that facilitates automated processing.

JSON has transformed development practices. It has fostered the growth of decoupled architectures where components communicate through well-defined interfaces. Its ease of manipulation has encouraged the adoption of functional and reactive paradigms. Development tools have integrated specific features for working with this format, from syntax highlighting to automatic validation.

The JSON specification is deliberately minimalist. Its designers chose to preserve the original simplicity rather than add features. Specific needs are covered by extensions and complementary tools that don’t affect basic compatibility. This stability ensures the format’s longevity in a constantly evolving technological environment.

The format was not imposed by a standardization body but naturally adopted because it met a real need. Its success stems from its alignment with existing practices and its ability to remain simple when so many other solutions sought complexity. JSON has become a pillar of modern web infrastructure, one of those elements we no longer notice because they seem so self-evident.