A History of Document Formats: Adobe Camelot, Binary Streams, and compilation to WASM

In the early days of computing, sharing documents across different computer brands was a nightmare. A document created on an Apple Macintosh would compile into gibberish when loaded on a Microsoft DOS PC because there was no unified language for text layout, fonts, and graphics. In 1991, John Warnock (co-founder of Adobe) wrote a research paper outlining 'The Camelot Project.' His goal was to define a universal system to display documents identically on any screen or printer. This project birthed the PDF format, built upon the PostScript layout language.

Concurrently, word processors relied on binary document formats (like Microsoft's legacy .doc streams). These binary structures were direct memory dumps of the program's internal objects, making them highly complex to parse by third-party applications. To increase interoperability, the industry moved to XML-based standards in the mid-2000s, leading to Office Open XML (OOXML, which defines modern `.docx` files). A `.docx` file is actually a renamed ZIP archive! If you rename a `.docx` file to `.zip` and extract it, you will find a folder structure containing plain XML files representing document texts, styles, and embedded media assets.

As document management migrated to the web browser, developers were faced with a dilemma. Web browsers only run JavaScript natively, which is a high-level, garbage-collected scripting language. Rewriting C/C++ compilation suites (such as PDF renderers and ZIP compressors) in JavaScript would result in massive performance degradation. The breakthrough came with WebAssembly (WASM). By compiling low-level languages directly into WASM bytecode, developers can run legacy document engines inside browser tabs. We can now run decades-old, high-performance C libraries natively in a web browser, bringing desktop-grade document processing safely to client-side pages.