CodeHistory.org
FIELD NOTE / 2026.09.213 MIN READ / 8 SOURCES

The Minds Behind AJAX and Rich Web Applications – 7 People Redefining Software

Seven developers and advocates helped turn asynchronous JavaScript, JSON, and cross-browser toolkits into the rich Web application model.

Written byTheo MercerEDITOR · CODEHISTORY RESEARCH DESKRESEARCHED / CITED

TL;DR

Ajax became a movement when Garrett gave a name to asynchronous browser/server interaction; Eich’s JavaScript provided the programming substrate; Crockford’s JSON simplified data exchange; Resig’s jQuery and Russell’s Dojo made cross-browser implementation practical; Almaer and Galbraith built the developer conversation around rich Web applications.[1][4][7]

Why you should read it anyway

Before Ajax-style interaction became common, Web applications often forced users into a click-wait-full-page-reload cycle. Background requests and partial updates made the browser feel more like a persistent application, enabling mail, maps, editors, dashboards, and eventually single-page applications.

Imagine where AJAX and Rich Web Applications would be without them

Without this movement, rich Web interaction would still develop through proprietary plugins, Java applets, browser-specific DHTML, or heavier server-rendered interfaces. The open standards stack would take longer to become competitive with desktop application experiences.

Time Estimate of how many years we would be hindered without them for human progress

Editorial counterfactual estimate: 3–7 years. The underlying APIs already existed; the breakthrough was shared vocabulary, better libraries, JSON, and developer education that made the pattern mainstream.

The 7 people behind AJAX and Rich Web Applications

1. Jesse James Garrett

Why they matter: Garrett coined “Ajax” in his February 2005 essay describing a model in which JavaScript exchanges data with servers asynchronously and updates the interface without reloading the whole page.[1] He did not invent XMLHttpRequest or every underlying technique; his contribution was naming and synthesizing a pattern developers could recognize and reproduce.

2. Brendan Eich

Why they matter: Eich created JavaScript, the client-side language that made Ajax-style interaction programmable in the browser.[6] Ajax depended on several browser APIs, but JavaScript supplied the event and application logic that coordinated network requests with DOM updates.

3. John Resig

Why they matter: Resig created jQuery and quickly integrated Ajax helpers into the library in 2006.[2][3] jQuery’s major contribution was smoothing over browser inconsistencies, making dynamic DOM manipulation and asynchronous requests far easier for ordinary developers.

4. Douglas Crockford

Why they matter: Crockford popularized JSON as a simple data-interchange format derived from JavaScript object syntax.[7] JSON became a natural payload for Ajax and later Web APIs because it mapped directly into JavaScript data structures without the verbosity of XML.

5. Alex Russell

Why they matter: Russell co-created Dojo, one of the major early JavaScript toolkits for rich browser applications.[4] Dojo wrapped XMLHttpRequest and many browser differences behind reusable APIs.[5] His contribution was framework infrastructure for applications that behaved more like desktop software.

6. Dion Almaer

Why they matter: Almaer became a prominent chronicler and advocate of the Ajax movement through conferences, writing, and the Ajaxian community. Historical conference material places him among the core public voices around Ajax-era application architecture.[8] His contribution was ecosystem-building and knowledge dissemination rather than invention of XMLHttpRequest.

7. Ben Galbraith

Why they matter: Galbraith likewise helped popularize Ajax practices through Ajaxian, books, conferences, and developer education.[8] In this roster he represents the community layer that transformed isolated techniques into a recognizable professional discipline for rich Web application development.

How they each differ from one another

Garrett named and synthesized the pattern; Eich supplied JavaScript; Resig and Russell provided practical libraries; Crockford supplied the data format that became dominant; Almaer and Galbraith built community and education. Ajax history is mostly about making existing browser capabilities usable as a coherent application architecture.

Final Take

Ajax changed the mental model of the Web page. Instead of a document replaced on every action, the page became a long-lived program that could fetch data and update itself incrementally. Modern front-end frameworks inherited that shift almost completely.

RESEARCH / PROVENANCE

Works Cited

8 SOURCES
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08

CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.

Contribute / Corrections

Improve the record.

Use this moderated submission form to suggest a correction, provide a source, challenge a priority claim or identify a missing contributor. Submissions are treated as research leads, not automatically published comments.

Submit a research lead

Please do not submit confidential material or claims you cannot support.