Posts Tagged: NCSA Mosaic

API Documentation as a Product (1990–1994): When the Web Learned to Explain Itself

Between 1990 and 1994, the Web’s earliest HTTP interfaces pushed a surprising innovation: documentation that behaved like a product. In Chapter 69, see how URLs, hypertext manuals, and early developer expectations set patterns that web APIs still follow.

Chapter 64: Multimodal APIs Before “APIs” — How Early HTTP Enabled Image + Text Workflows (1990–1994)

From the first HTTP requests to early browsers like Mosaic, the Web’s 1990–1994 era pioneered practical image+text workflows that foreshadowed today’s multimodal APIs.

Chapter 59: Before Permission Prompts — How the 1990–1994 Web Shaped Privacy by Limitation

In the Web’s earliest years, browsers didn’t ask for camera, location, or notification access—because they couldn’t. This chapter traces how early HTTP and HTML interfaces quietly defined privacy expectations long before formal browser permissions APIs existed.

E-commerce APIs Before “APIs”: Programmable Storefronts in the Web’s First Years (1990–1994)

In the Web’s earliest era, storefronts became “programmable” long before the term API was mainstream. From HTTP’s minimalist request/response model to HTML forms and CGI, the early 1990s set the template for e-commerce endpoints, carts, and integrations.

Chapter 51 (1990–1994): Before “Cloud APIs” — How Early HTTP Interfaces Sparked Infrastructure Automation

Long before today’s cloud provider APIs, early HTTP servers, HTML forms, and CGI scripts (1990–1994) taught developers a powerful idea: infrastructure can be controlled through simple, stateless web interfaces.

Jamstack Before Jamstack: Build-Time API Consumption at the Birth of the Web (1990–1994) — Chapter 49

Long before “Jamstack” had a name, early Web builders were already practicing its core idea: prebuilding pages from remote data. In 1990–1994, HTTP’s simple request/response model, early gateways, and CGI scripts laid the groundwork for build-time API consumption—even if nobody called it that yet.

Chapter 28: Before WebSockets — Real-Time Web Communication Dreams in the Web’s First HTTP Interfaces (1990–1994)

In the Web’s first years, HTTP’s simple request/response model made “real-time” feel out of reach. This chapter traces the early interface patterns—HTTP/0.9, evolving headers, and CGI scripts—that set the stage for later solutions like the WebSocket API.

Chapter 16 (1990–1994): The Early Web Interfaces That Made Twitter-Style APIs Possible

From URLs and early HTTP methods to CGI and the first dynamic web interactions, the 1990–1994 era laid the interface patterns that later powered Twitter API integrations and modern social platform APIs.

XMLHttpRequest Before It Existed: How 1990–1994 Web Interfaces Set Up the AJAX Era (Chapter 10)

XMLHttpRequest and AJAX didn’t arrive in the early 1990s—but the Web’s first HTTP interfaces did. This chapter explains the 1990–1994 foundations (URLs, HTTP requests, forms, and CGI) that made asynchronous web APIs inevitable.

HTTP’s First Steps (1990–1994): How the Web’s Original Protocol Became the Foundation of Web APIs

Before “web APIs” had a name, early HTTP and the newborn World Wide Web (1990–1994) established the core patterns APIs still use: resources, stateless requests, URIs, and a simple request/response contract.