The Web That Never Was - Dylan Beattie
NDC Conferences
AI-assisted summary of The Web That Never Was - Dylan Beattie — original source. Check the original for full context.
Source published:
Key ideas
- Technological dominance in software is rarely determined by Darwinian survival of the fittest; everyday tools and standards often succeed because they were merely 'good enough' to overcome analysis paralysis and historical accidents. (5:16)
- Modern computing and the web hinge on narrow historical forks, such as IBM's fateful 1981 operating system deal and the hasty 10-day creation of JavaScript under corporate deadlines. (54:09)
- Dylan Beattie constructs an alternate history—featuring the GRID protocol, HyperLisp, and Gary Kildall's dominance—to illustrate how arbitrary choices shape our digital landscape. (18:40)
Detailed notes
## Background Published by NDC Conferences on YouTube on November 13, 2018, this keynote presentation features software developer Dylan Beattie. According to the page description, the talk investigates an alternate history of the World Wide Web, exploring what the software industry might look like without Microsoft, Windows, Google, or JavaScript if past compromises and corporate meetings had unfolded differently.
## TL;DR Dylan Beattie weaves an elaborate counterfactual history of computing where Gary Kildall’s Digital Research dominates the PC market over Microsoft, Tim Berners-Lee establishes 'the GRID' using SQL verbs and tilde-based markup instead of the World Wide Web, and HyperLisp replaces JavaScript. In this timeline, Marc Andreessen and John Carmack team up to build networking for Nintendo, PerfectDigital launches GEM 95, and Steve Jobs unveils an ultra-thin anodized NeXT laptop powered by a search engine called Goggle. Beattie then dissects the real-world near-misses behind these scenarios—from Brendan Eich's original intent to embed Scheme into Netscape to Tim Berners-Lee's regret over the double-slash in URLs. The presentation concludes that modern technology is defined not by Darwinian perfection, but by pragmatic, 'good enough' compromises that helped engineers move forward.
## Atmosphere & style The presentation opens with an engaging acoustic parody of Baz Luhrmann's 'Wear Sunscreen' before settling into a warm, comedic blend of speculative fiction and deep computer history. Beattie commands the stage with dry wit, theatrical pacing, and palpable affection for obsolete hardware and retro software trivia. Watching the talk feels like sitting through a clever, geeky stand-up routine that successfully morphs into a thoughtful meditation on engineering pragmatism and the arbitrariness of technological fate.
## Bulletin - [05:16](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=316s) Technological dominance in software is rarely determined by Darwinian survival of the fittest; everyday tools and standards often succeed because they were merely 'good enough' to overcome analysis paralysis and historical accidents. - [54:09](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3249s) Modern computing and the web hinge on narrow historical forks, such as IBM's fateful 1981 operating system deal and the hasty 10-day creation of JavaScript under corporate deadlines. - [18:40](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1120s) Dylan Beattie constructs an alternate history—featuring the GRID protocol, HyperLisp, and Gary Kildall's dominance—to illustrate how arbitrary choices shape our digital landscape.
## Key takeaways - [05:16](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=316s) Technological adoption is driven by pragmatic compromises, technical debt, and arbitrary timing rather than objective technical superiority. - [05:16](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=316s) Douglas Adams' three rules of technology illustrate that what exists at birth feels natural, what appears between ages 15 and 35 enables careers, and anything after age 35 violates the natural order. - [08:44](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=524s) IBM's inability to move quickly due to corporate bureaucracy led to an isolated skunkworks project that built the original PC using off-the-shelf parts. - [12:01](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=721s) Before Paul Mockapetris independently designed DNS, all internet host mapping was manually managed in a centralized HOSTS.TXT file at the Stanford Network Information Center. - [15:26](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=926s) Competing hypermedia platforms like the University of Southampton's Microcosm stored links in external databases rather than embedding them directly in documents. - [18:40](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1120s) In an alternate timeline, Tim Berners-Lee designs 'the GRID' using SQL-style HTTP verbs to preserve neat, fixed-width server logs. - [24:04](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1444s) The alternate timeline eliminates angle brackets and URL double slashes in favor of tildes (~) and exclamation marks (!) based on ASCII character frequencies. - [27:36](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1656s) Digital Research's Gary Kildall could have captured the PC operating system monopoly by recognizing the value of licensing CP/M-86 to third-party clone makers. - [31:43](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1903s) A redirected career path where Marc Andreessen and Jim Clark join Nintendo to develop console networking leaves browser innovation open to competitors. - [35:46](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=2146s) Instead of JavaScript, an alternate web standard embeds HyperLisp, leveraging prefix syntax, first-class lambdas, and continuation-passing style for asynchronous client-server interactions. - [57:04](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3424s) Real-world tech history shows that Brendan Eich was originally hired to put Scheme into Netscape before rushed commercial deadlines mandated curly-brace JavaScript. - [54:09](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3249s) Tim Berners-Lee has openly acknowledged that the double slash in URL protocols was completely redundant and could easily have been omitted. - [57:04](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3424s) Major software giants exist due to near-misses, including Excite turning down an $800,000 acquisition offer for Google in 1999 and Apple almost buying BeOS instead of NeXT. - [01:01:05](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3665s) Progress in the software industry comes from taking pragmatic, 'good enough' steps forward rather than stalling under analysis paralysis.
## Detailed walkthrough ### [00:06](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=6s) Advice for the Class of '17: The "Wear Sunscreen" Parody
Dylan Beattie opens his keynote with a musical parody of Baz Luhrmann's 1997 spoken-word hit "Everybody's Free (To Wear Sunscreen)", offering humorous, hard-won software engineering wisdom to the "class of '17." Subverting the original song's advice to wear sunscreen, Dylan insists that using flat screens is the single most vital tip for the future: “The benefits of flat screens have been proved in Hollywood whereas the rest of my advice has no basis more reliable than my own meandering experience.” He tells developers to revel in the fleeting optimism of greenfield projects, warning that they will never truly appreciate that confidence until things inevitably break, only to look back after shipping and realize how surprisingly productive they were. He takes aim at common architectural anxieties, pointing out that worrying about changing database vendors is largely pointless: “Don't worry about changing database providers or worry, but know that every company who used an ORM in case they needed to switch databases never actually did it.” Instead, the genuine dangers are unpredictable external dependencies—like an engineer abruptly resigning at 4:00 p.m. on a quiet Tuesday.
Interspersing his monologue with rhythmic imperatives—*optimize*, *rebase*, *refactor*, *re-read*—Dylan touches on modern software culture, ego, and tooling. He warns against obsessing over frameworks, emphasizing that end users only care about the final experience, not the tools used to construct it. He urges developers not to feel insecure if they do not understand functional languages like F#, noting that he has worked with stellar junior developers and veteran system architects who do not know it either. Above all, he highlights mental health and sustainability: taking breaks and guarding against burnout, because the human brain is the most powerful computer any developer will ever possess. Developers must accept inevitable truths: code will have bugs, deadlines will be missed, and anyone might one day end up in management, where they will look back through rose-tinted glasses and imagine that their past code was flawless and developers diligently tuned their database indexes.
- **On code maintenance:** Do not reformat someone else's codebase, and do not tolerate people arbitrarily reformatting yours. - **On hardware:** Hold onto old hard drives, but throw away obsolete network cards. - **On community and media:** Remember positive retweets, ignore online flame bait, and never read YouTube comments because they will only induce rage. - **On engineering practices:** Cache your package dependencies against sudden disappearance; inspect log files as the primary early-warning system for failures; and never deploy to production without automated integration tests or QA. - **On programming languages:** Write code in x86 Assembler once until before it makes you smug, and write Visual Basic once before it makes you stupid. - **On open source:** Sharing code is noble, but it requires far more effort than simply slapping a `README` onto a stray project folder and uploading it to GitHub in the hope that strangers will resolve your bugs.
---
[05:16](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=316s) Douglas Adams and How We Experience Technology
Transitioning to the keynote address, Dylan greets the Sydney audience, asks if they are enjoying the conference and attending PubConf, and introduces a framework for understanding human perceptions of innovation borrowed from author Douglas Adams. Adams proposed a set of rules describing how people process technological change throughout their lives. Dylan summarizes Adams' rule: “Anything that is in the world when you're born is normal, it's just a natural part of the way the world works; anything invented between when you're 15 and 35 is new and revolutionary and you can probably get a career in it; anything invented after you're 35 is against the natural order of things.” Dylan maps his own biography onto this curve: born in 1978—just too late to see the original *Star Wars* in theaters—he entered a world where color television, mainframe computers, and the ARPANET were already established realities.
The World Wide Web arrived right around when Dylan turned 15, allowing him to forge a career as a webmaster learning HTML. Conversely, items that arrived after he crossed the age of 35—such as the Apple Watch, fidget spinners, and the dance move known as "dabbing"—instinctively feel unnatural and alien to him. Dylan uses this to emphasize that human reactions to technology are deeply subjective and tied to the exact moment an individual first encounters an invention. Quoting Adams again, he reminds the audience that technology is simply "stuff that doesn't work yet"; once it works reliably, it fades into the background as ordinary "stuff," much like chairs, which no longer fail and are therefore never considered technology.
Dylan cautions against the comforting myth that technological progress follows an orderly Darwinian path:
```mermaid flowchart LR accTitle: The Myth of Technological Evolution accDescr: A flow showing prototypes evolving into production systems through supposed natural selection versus reality. subgraph Myth["The Darwinian Myth"] A["Prototypes & Ideas"] --> B["Survival of the Fittest"] B --> C["Best Solution Wins"] end subgraph Reality["The Historical Reality"] D["Gaffer Tape & Tech Debt"] --> E["Dumb Luck & Market Flukes"] E --> F["Entrenched Standards"] end ```
Every piece of ubiquitous equipment today originated as fragile prototypes, hacks, and technical debt held together with gaffer tape, code, and string. He cautions that it is dangerous to assume the best technical solution always triumphs: “It's easy to think that there is some sort of Darwinian survival of the fittest that we have all these prototypes and all these ideas and all these solutions to problems like smartphones and digital communication and the best solution is going to win, but that is absolutely not true.” Instead, history turns on mundane accidents, compromises, and arbitrary choices.
---
[08:44](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=524s) The IBM PC and the Roots of the Personal Computer Era
To demonstrate how arbitrary decisions shaped modern computing, Dylan takes the audience back to the late 1970s. In the beginning, IBM reigned supreme over the computing landscape with the mainframe. Dylan references the apocryphal remark attributed to Thomas J. Watson—the IBM chairman after whom the Watson AI platform is named—speculating that the entire world market might ultimately have room for only about five computers. Over the post-war decades, computing transitioned from vacuum tubes (valves) to discrete transistors and integrated circuits, and software moved from direct machine code to assembly and high-level interpreted or compiled languages. Gradually, computers escaped universities and research labs to inch toward the home.
By the late 1970s, IBM commanded an absolute corporate monopoly over information technology. Dylan points out that while modern giants like Alphabet, Apple, and Amazon possess immense sway, competitors still successfully sell alternative laptops and phones; in contrast, IBM virtually owned the entire sector. Recognizing that personal computers were no longer a fringe hobbyist market and that Watson’s five-computer limit was completely wrong, IBM resolved to create a computer that an ordinary consumer could fit into the back of a car and carry home. However, IBM’s colossal bureaucracy was notoriously slow:
> “IBM in the '70s was a juggernaut: you couldn't steer it. It was this massive enterprise that was incapable of doing anything quickly because it would take six weeks just to approve the font for the purchase orders.”
Terrified of being left behind by nimbler rivals, IBM formed an isolated skunkworks team to construct the IBM Personal Computer (the PC). They made the radical choice to abandon their traditional vertical manufacturing and instead assemble the machine entirely from commercial off-the-shelf components sourced worldwide: motherboards, Intel processors, and serial buses from manufacturing hubs in Taiwan, China, and Singapore. The only critical missing ingredient was an operating system, sending IBM shopping for the premier operating system company of 1981. Meanwhile, parallel to IBM's consumer hardware push, the military's Advanced Research Projects Agency (ARPA) was pioneering resilient computer networks designed to withstand Cold War attacks, setting the stage for the protocols that would eventually underpin the global network.
[12:01](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=721s) From ARPANET Maps to TCP/IP and the Scaling Limits of the HOSTS File
Dylan Beattie shows an ARPANET map from 1973, pointing out that before it became the internet, every single device on the network and what software it was running was drawn by hand by a draftsperson with pen and paper. Around 1981, the specification for IPv4 was published, and on January 1st, 1983—a date known as “Flag Day”—a strict rule went into effect: “that was the day they said from now on everything connected to our network must run TCP/IP, that's it.” In 1982, SMTP (Simple Mail Transfer Protocol) was ratified, finally providing both a system for computers worldwide to communicate and a way for human operators to exchange email.
As the network expanded, it ran into one of the fundamental hurdles of computer science: naming things. Before DNS was created, adding a new server required plugging it in and literally calling Elizabeth "Jake" Feinler at the Network Information Center (NIC) at Stanford: “Jake, I got a new computer, can you add it to the hosts file please?” Organizations kept track of connected systems through that single `HOSTS.TXT` file, which was copied via overnight FTP during cheaper phone rates, ferried back on tape, or picked up in person by someone visiting Stanford for a meeting. The operational limitations were severe:
> “If you wanted to add a machine to the hosts file on a public holiday you couldn't, because the people who had permission to edit the file were all off celebrating.”
Machines could not be added at night, over the weekend, at Thanksgiving, or at Christmas. While manageable when the network was small, the approach could not survive the growth of the internet.
[14:14](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=854s) Paul Mockapetris and the Invention of Scalable DNS
To replace the manual hosts file, the University of Southern California tasked Paul Mockapetris with evaluating five competing engineering proposals to find a compromise that kept everyone happy. Beattie quips about USC's storied past—noting it also gave the world Unix and LSD—before praising Mockapetris's actual decision:
> “He looked at all five of these solutions, went 'these are all crap,' and threw them away, and he designed and invented by himself DNS.”
Mockapetris created a hierarchical database of hostnames and network addresses engineered to scale naturally with network complexity. The design ensured that as more hosts joined, the proliferation of DNS servers distributed the load, cached responses locally, and reduced root-level lookups. Because of this self-scaling architecture, DNS has survived virtually unchanged from its original specification, continuing to power hundreds of millions of domain names today.
```mermaid flowchart TD accTitle: Evolution of Internet Host Naming accDescr: Diagram contrasting the centralized HOSTS.TXT system at Stanford with the decentralized, hierarchical DNS architecture.
subgraph Centralized["Pre-DNS Architecture"] NIC["Stanford NIC<br/>Central HOSTS.TXT File<br/>(Jake Feinler)"] ClientA["Host A"] -->|"Phone call / Manual FTP"| NIC ClientB["Host B"] -->|"Tape copy / Nightly transfer"| NIC end
subgraph Distributed["Mockapetris DNS Architecture"] Root["Root Nameservers"] TLD["TLD Nameservers (.com,.org)"] Auth["Authoritative Nameservers"] Local["Local Caching Resolvers"]
Root --> TLD TLD --> Auth Auth -.->|"Cached records"| Local end ```
[15:26](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=926s) Tim Berners-Lee, "Vague But Exciting," and Alternative Hypermedia
By the late 1980s, the necessary foundation was laid: commodity hardware was cheap, and TCP/IP, DNS, and SMTP were working standards. At CERN on the French-Swiss border, Tim Berners-Lee—who still proudly uses the official job title “Web Developer”—observed that his mathematician and physicist colleagues lacked a digital medium to publish and cross-reference academic research. He drafted a proposal titled *Information Management* and submitted it to his supervisor, who returned it with the famous note: “vague but exciting.”
Beattie emphasizes that the web's eventual dominance was not inevitable. While studying at the University of Southampton in 1997, two of his professors recalled presenting their own competing hypermedia platform, Microcosm, at an international conference just before Berners-Lee took the stage to pitch the World Wide Web. Microcosm ran on Windows 3.1 and operated on a fundamentally different philosophy: it rejected embedded hyperlinks so users would not have to rewrite existing files. Instead, it ran an independent link database alongside untouched text, RTF, or WordPerfect documents, presenting hypermedia links in a companion window curated by information analysts and librarians. While the web overtook it for public browsing, that core link-indexing technology survived into a commercial incarnation called Multicosm PLC, serving large-scale legal discovery for subpoenaed corporate servers.
[18:40](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1120s) Alternate Timeline: The Grid and SQL-Style HTTP Verbs
Transitioning into an alternate-history narrative with an homage to *The Twilight Zone*, Beattie reimagines early 1990s CERN. In this timeline, Tim Berners-Lee is experimenting with an information system he originally called "the Mesh." While contemplating the name "World Wide Web," the network goes down, forcing him to describe the concept over the telephone:
> “He picks the phone up and he goes, 'Yeah, it's this WWW,' and they say, 'Hang on a second, that acronym is actually longer than the thing it's short for; if this catches on it might sound a little bit daft.'”
Conceding the point over afternoon tea, Berners-Lee solicits alternatives from colleagues. Suggestions include: - The "International Information Interchange" (the `iii`), quickly mocked because “it sounds like pirates.” - The "Multinational Metadata Matrix," suggested by an engineer who had just finished reading William Gibson's *Neuromancer*. - The winning compromise: the "Global Repository of Interlinked Documents"—**the GRID**.
Needing a transfer protocol, Berners-Lee coins Hypertext Transfer Protocol (HTTP) but borrows its operational verbs directly from SQL rather than the familiar methods of our timeline. To keep fixed-width server log files neatly aligned, every verb is designed with exactly six letters: - `SELECT`: fetch a document from a server. - `CREATE`: publish a new document onto the Grid. - `UPDATE`: modify an existing document with corrections. - `DELETE`: remove a document when legal demands require it. - `SUBMIT`: send instructions or parameters to a remote system to execute tasks.
[21:57](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1317s) Designing the Grid: From SURF to the Bang Syntax
In this alternate timeline, Tim Berners-Lee works on standardizing how documents are addressed across a distributed network. He develops the Standard Unique Resource Finder (SURF), musing that the phrase might actually catch on when people talk about "surfing the grid." His initial concept includes the entire URL structure we know today: `http://user:pass@grid.domain.com:port/path?query#fragment`. However, a colleague immediately challenges him on including authentication details right in the visible address bar: “Why are you putting username and password credentials in plain text on something that's going to be part of the user interface?” Tim realizes the obvious hazard and immediately agrees: “Good point. We shouldn't support that; that would be stupid.”
With credentials removed, Tim continues streamlining the address format. Queries and fragments are made optional, relegated purely to search and indexing tasks, and default documents are introduced so users can simply address `grid.domain.com`. Looking critically at the remaining elements, he questions the UNIX file system inheritance of the double slash: “What is the slash-slash thing? That is... you know, he got it from UNIX file systems, but this isn't a file system; this is a completely new thing. Let's get rid of it.” When someone raises a technical concern that a numeric host name could collide with port numbers, he replaces the colon-slash notation entirely with an exclamation point delimiter: `http!grid.domain.com`. He then introduces an elegant shortcut: if a host shares its name with the protocol in use, you can drop the protocol segment altogether. The final, fully qualified address for a default server document becomes simply `grid!domain.com`. When a team member asks, “Tim, don't you think grid!cern.ch sounds a bit silly?”, Tim retorts with devastating common sense: “Not as silly as http://www.cern.ch.”
```mermaid flowchart TD accTitle: Alternate Address Evolution accDescr: The step-by-step simplification of Tim Berners-Lee's grid resource addresses.
subgraph InitialDraft ["1. Verbose Draft"] A["http://user:pass@grid.domain.com:port/path?query#fragment"] end
subgraph Cleanups ["2. Trimming & Delimiters"] B["Drop plain-text credentials"] C["Make queries and fragments optional"] D["Remove UNIX slash-slash (//)"] E["Switch to bang (!) to avoid numeric host/port collisions: http!grid.domain.com"] end
subgraph FinalAddress ["3. The Default Convention"] F["grid!domain.com"] end
A --> B --> C --> D --> E --> F ```
[24:04](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1444s) HTML Without Angle Brackets: The Tilde Revolution
Next, Tim tackles the presentation layer for hypermedia documents. Turning to Standard Generalized Markup Language (SGML)—used since the early 1980s in industrial typesetting—he drafts HTML version 0.1. However, CERN is a high-energy physics laboratory filled with mathematicians and physicists whose scientific texts are packed with mathematical inequality symbols. They push back fiercely: “Please don't use angle brackets. Like, literally every document we've got will break the second we try and publish it on your grid system, because we use those angle brackets for something else.”
Taking their complaint seriously, Tim runs a frequency analysis across all plain text files across CERN's FTP servers and network shares to discover the least frequently used character in basic ASCII. The winner is ASCII character 126 (hex `0x7E`): the tilde (`~`). Tim immediately adopts the tilde as his language's fundamental markup signifier. He sets an ingenious baseline rule: a double line break represents a paragraph break. Because existing plain-text files already use double carriage returns and avoid tildes, vast archives of scientific writing become instantly valid Grid documents with zero manual editing. By February 1992, he releases HTML 0.2, introducing structured metadata blocks, a clean `:key value` syntax, headings, paragraphs, image embedding, and a tag called `link`. When an associate asks why he doesn't call it an "anchor," Tim rejects the idea outright: “What is anchor? Why would you call it that? That makes no sense.”
- **The Tilde (`~`)**: Selected via ASCII frequency analysis (code 126 / `0x7E`) as CERN's least-used character to prevent collisions with mathematical formulas. - **Double Line Break**: Preserved as native paragraph breaks so legacy text files immediately render as valid documents. - **HTML 0.2 Features**: Explicit document metadata for machine indexing, visible body text for users, clean attribute syntax, native image inclusion, and the self-explanatory `link` tag instead of the cryptic `<a>`.
[26:34](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1594s) Grid Fever and NCSA Mosaic
With the specification published online in February 1992, widespread enthusiasm takes hold across the tech landscape. Dylan describes the onset of global "grid fever," where commercial demand explodes overnight. Individuals take weekend crash courses, print fresh business cards claiming to be "grid masters," and launch lucrative consultancies on the premise that clients have no idea what they are doing either—an environment Dylan jokes is precisely how he landed his own first job in technology.
The technology hits an inflection point with the release of NCSA Mosaic by the National Center for Supercomputing Applications at the University of Illinois. Mosaic serves as an open-source, graphical multi-protocol client: - Displays full inline graphics and hypermedia documents over the new Grid protocol. - Integrates legacy protocols seamlessly, allowing users to browse Usenet via NNTP, navigate Gopher menus, and transfer files over FTP. - Unifies disparate internet tools into a single visual window, making the wider computing world sit up and take notice.
[27:36](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1656s) Gary Kildall's Masterstroke: The Triumph of Digital Research
Dylan circles back to the pivotal turning point in personal computing: IBM's search in the early 1980s for an operating system for their upcoming PC. Instead of turning to Microsoft, IBM approaches the premier microcomputer system architects of the era: Gary Kildall and Digital Research. Kildall grasps a fundamental reality that completely eludes the executives at Big Blue: “What Gary Kildall has realized and IBM haven't is that if your flagship computer is made out of off-the-shelf parts that you bought from China and Singapore and Taiwan, you don't actually own anything.” Kildall understands that when hardware is commoditized, the operating system holds all the true platform value.
Kildall strikes a brilliant non-exclusive licensing bargain: he sells IBM a license to distribute CP/M-86 at a 50% discount in exchange for retaining the unrestricted right to sell the operating system to other vendors. IBM launches the PC with CP/M-86, while Digital Research continues rapid development. When IBM releases the 16-bit PC/AT in 1984, Digital Research is ready with MP/M-86 (Multi-Programming Monitor for Microcomputers). It delivers true protected-mode multitasking on the Intel 80286 processor, cleanly sidestepping the infamous 640 KB conventional memory wall. As low-cost beige PC clone manufacturers flood the global market, they all license Digital Research's software. By the time IBM realizes they gave away the farm, Digital Research is exploding into the largest technology titan on Earth.
[29:47](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1787s) Steve Jobs, NeXT, and the Rise of PerfectDigital
Meanwhile, in California, Apple faces fierce corporate turmoil. Following a hostile board takeover in 1987, shareholders oust Steve Jobs from the company he co-founded. Dylan recounts how Jobs, determined to prove them wrong, sets up shop right across the street and founds NeXT. He turns his back on common beige plastic aesthetics and introduces the NeXTstation: a striking eight-inch matte-black magnesium cube costing $10,000—vastly outpricing commodity $800 IBM clones. The machine is aimed squarely at high-end cinema production, scientific research, and advanced software engineering. Tim Berners-Lee procures one of these NeXT computers at CERN, using its advanced development environment to build and run the world’s very first grid browser (appropriately titled `GridBrowser.app`).
At the same time, Digital Research executes an industry-shaking consolidation by merging with the world's second-largest software outfit, the WordPerfect Corporation. Dylan notes that while the US Department of Justice spends 18 months fretting over the monopoly—crying, “Something must be done! We can't have a company that powerful! Won't somebody think of the children?”—regulators fail to stop the deal. The merger finalizes under the banner of **PerfectDigital**. Armed with the world’s most dominant operating system, an industry-standard word processor, and an unrivaled office suite, PerfectDigital sits poised to dictate the future of computing.
[31:43](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1903s) The Nintendo Opportunity and the Death of Mozilla
In this alternate timeline, Perfect Digital needs a browser to let users navigate "the Grid" from their operating system platform. To solve the problem, they seek out two prominent figures in the computing scene. The first is Jim Clark, founder of Silicon Graphics, who spent the 1980s engineering high-performance 3D graphics workstations. The second is Marc Andreessen, fresh out of the National Center for Supercomputing Applications (NCSA), where he had been one of the co-creators of the pioneering NCSA Mosaic browser. Both have recently left their respective posts and are exploring new ventures. Their initial impulse is to build an outright "Mosaic killer" under the project code name "Mozilla" (“how about that for a name”).
Before that effort can take off, the phone rings. Nintendo Corporation reaches out with an enticing proposition: they are developing their next-generation console, the Nintendo 64, and want players to be able to plug into a wall phone jack to play titles like *Mario Kart* and *Donkey Kong* against friends worldwide. Clark and Andreessen reflect on the offer and decide it is too compelling to pass up; as Dylan Beattie notes, “the Mozilla project never happens.” They relocate to Seattle to join Nintendo, abandoning their browser plans entirely.
Upon arriving at Nintendo's Seattle office, Clark and Andreessen encounter another formidable duo: John Carmack and John Romero. A couple of years earlier, powered by pizza, caffeine, and an intense marathon weekend, Carmack and Romero had ported *Super Mario Bros. 3* to run on MP/M-86. They delivered a disk to Nintendo demonstrating smooth side-scrolling performance squeezed out of a humble 286 CPU—a technical feat widely deemed impossible at the time. Nintendo was so impressed that they hired both programmers on the spot. With Nintendo bankrolling the dream team, Clark (the workstation hardware pioneer), Andreessen (the network browser engineer), Carmack (“probably the finest graphics programmer of any generation”), and Romero (“who's quite good at level design and having good hair”) disappear into secret console development, leaving the browser space wide open.
```mermaid flowchart TD accTitle: The Divergent Browser Founders accDescr: Flowchart showing how Jim Clark and Marc Andreessen join Nintendo instead of creating Netscape/Mozilla.
subgraph BrowserTrack["Abandoned Browser Plans"] A["Jim Clark (Silicon Graphics)"] & B["Marc Andreessen (NCSA Mosaic)"] C["Proposed Project: 'Mozilla' (Mosaic Killer)"] A --> C B --> C end
subgraph NintendoConsortium["Nintendo Seattle Dream Team"] N["Nintendo 64 Network Initiative"] JC["John Carmack"] & JR["John Romero"] Mario["Ported Super Mario Bros. 3 to MP/M-86"] --> JC & JR N --> A & B JC & JR --- N end ```
[34:02](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=2042s) Cello, Grid Perfect, and the SAFE Protocol
With Andreessen and Clark off the market, Perfect Digital must look elsewhere. They are left with their GEM/3 desktop interface on a 286 visual operating system and still desperately need a grid browser. Scanning the next candidates on their list, they locate Thomas Bruce, a librarian running the legal library at Cornell Law School, who has authored an MP/M and GEM browser named Cello. Because WordPerfect is already the entrenched word-processing standard across American legal practices, Perfect Digital enjoys deep existing ties with the legal community.
A deal is struck rapidly to acquire Bruce’s Cello source code. Perfect Digital optimizes its underlying libraries, layers on new capabilities, and fits the software directly into its branded lineup alongside WordPerfect, LetterPerfect, and DataPerfect: "Grid Perfect." They bake in a crucial addition: SAFE, or Secure Application Frame Encryption. SAFE runs alongside the GRID (Global Repository of Internet Documents) protocol, marking the first time a grid client can communicate with a grid server without third parties sniffing or eavesdropping on transmissions.
This cryptographic foundation instantly ignites the protocol's built-in `SUBMIT` verb. The network expands far beyond mere document retrieval, updates, and deletions. Because Perfect Digital embeds core WordPerfect editing tools directly into the browser, every user who consumes the grid can also write to it; publishing capability is accessible from day one via integrated WYSIWYG authoring tools.
- **Grid Perfect Lineage**: Acquired from Thomas Bruce's Cello browser developed at Cornell Law School. - **Protocol Suite**: GRID combined with SAFE (Secure Application Frame Encryption) for secure end-to-end transmissions. - **Read/Write Integration**: Full WYSIWYG WordPerfect engines embedded inside the client turned every viewer into an immediate publisher.
[35:46](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=2146s) The Rejection of Java and the Triumph of HyperLisp
Static documents quickly prove restrictive for complex interactive software, prompting demand for an embedded programming language across clients and servers. In the mid-1990s business software landscape, Beattie notes the natural choice is Lisp—a half-century-old language with “your father's parentheses elegant weapons for a more civilized age.” At the same time, Paul Graham is steering his startup Viaweb, having realized that Lisp's native support for continuation-passing style is ideal for stateless grid protocols. Continuation passing enables server processes to snapshot execution state mid-stride and resume it later without persistent memory allocations or shared-state overhead.
Sun Microsystems attempts to derail this by pitching their own creation, Java—the cross-platform, object-oriented language they are pushing aggressively everywhere. Sun visits Perfect Digital and encourages them to adopt Java. When Perfect Digital mentions their existing language, HyperLisp, Sun asks if they might rename it to "JavaLisp" or "JavasScript" to ride the trend.
To resolve the issue, Perfect Digital invites Paul Graham in for an afternoon discussion. Graham lays out his programming philosophy, details Lisp's historical strengths, breaks down symbol types, and explains the concept he later popularized as the "Blub paradox"—the idea that programming languages are fundamentally unequal in power. By late afternoon, Sun's Java proposal is dead. Graham seals the case with two decisive arguments: 1. **Homoiconicity and State Mobility**: In HyperLisp, every piece of program code is an expression, and every expression is a data structure. Because the language is entirely homoiconic and mutable, developers never have to write serialization or deserialization layers. A running program can freeze its execution, serialize into a native data structure, travel across the network wire to a client, rehydrate instantly, and resume work where it stopped. 2. **The Economic Argument for the Bean Counters**: Graham appeals directly to the accountants by explaining that this architecture offloads compute to the user: “look this basically means everyone who starts using your application is effectively donating their computer to you so you can run code on that so you don't need to invest in so much infrastructure.” Much like DNS, application scalability naturally tracks user adoption.
[39:29](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=2369s) HyperLisp in Action: Asynchronous distributed scripting
HyperLisp becomes the universal client-server standard, cleanly embedded into HTML (specifically version 4.01, because version 4.0 had typographical errors in the specification). Code is embedded directly within web pages using Lisp's characteristic prefix notation. In the simplest use case, developers bind an event directly to an element:
```lisp (bind (document:load) (lambda (element event) (alert "Hello, world!"))) ```
Rather than treating the DOM as an awkward document object, HyperLisp uses native symbol types that map browser primitives directly into the runtime without requiring verbose namespacing.
```mermaid flowchart LR accTitle: HyperLisp Client-Server Execution Loop accDescr: Flowchart of a HyperLisp client firing an asynchronous grid-submit callback to a server and updating the DOM span.
subgraph ClientBrowser["Grid Perfect Browser"] DOM["HTML 4.01 Element"] Callback["(lambda (response)...)"] Span["DOM Span Update"] DOM -->|"submit event"| Callback end
subgraph ServerInfra["Grid Server"] Endpoint["Grid Processing"] end
Callback -->|"grid-submit (asynchronous)"| Endpoint Endpoint -->|"hydrated data response"| Callback Callback --> Span ```
In a more sophisticated example, a form's submit handler triggers an asynchronous callback across the network using a built-in `grid-submit` method. When the server returns data, the callback immediately assigns the response into a target `span` element:
```lisp (bind (form:submit) (lambda (element event) (grid-submit "/api/data" (lambda (response) (set-value! result-span response))))) ```
As Beattie points out with clear amusement, this delivers full asynchronous distributed computing out of the box—sparing this universe the fate of another timeline, where “in a parallel universe they take 10 years to invent and they'd call it Ajax and it would be horrible.” Arithmetic and function calls rely on prefix syntax, leaving hyphens completely free for identifier names. Because hyphenated variable names just work without clashing with subtraction operators, the community avoids decades of divisive debates over `camelCase` versus `snake_case`. Rich, first-class lambdas provide natural asynchronous communication right out of the box, establishing an elegant, unified foundation for distributed computing.
[04:11:37](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=15097s) GEM 95 and the Beatles Reunion
Perfect Digital launches GEM 95, heralded as their most powerful desktop operating system ever. To celebrate, they pull off the ultimate marketing coup: getting the Beatles back together for a massive launch party. The "Grid" browser is baked directly into the operating system from the ground up, and to encourage content creation, they ship a free version of WordPerfect. This version has no printer support, meaning its sole purpose is to let users author documents and publish them directly to the Grid.
The Beatles reunion is a sensation, and Perfect Digital capitalizes on it by featuring the browser's "back" button heavily in all of their marketing literature. The strategy is an overnight success, and the public falls in love with the seamless integration of the Grid. In this timeline, the future of computing looks incredibly bright—unless, of course, you happen to be working for Apple.
- **GEM 95 Launch:** Integrated Grid browser, bundled with a printer-free version of WordPerfect for Grid authoring. - **The Beatles Reunion:** The band reunites for the launch party, and the browser's "back" button becomes a central marketing icon.
[04:12:18](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=15138s) Apple's Struggle and the Rise of BeOS
At Apple, things have gone from bad to worse. Having previously ousted Steve Jobs, the board is now deeply regretting the decision as the company flounders. During a tense board meeting, CEO Gil Amelio tentatively suggests a radical move: buying NeXT to bring Steve Jobs back. The board flatly rejects the idea. As Dylan Beattie notes, “They laugh him out of the room this is the dumbest idea and there is no way Steve Jobs is ever going back to Apple after the way they kicked him across the street.”
However, Jobs is not the only visionary engineer to have left Apple. A startup called Be Incorporated, founded by former Apple executives, has developed BeOS. This brand-new, ground-up, high-performance operating system features dedicated multi-threading designed specifically for streaming media, real-time communication, and audio processing. While the software is brilliant, Be Incorporated is struggling to manufacture and sell the physical computer hardware to run it. Recognizing this bottleneck, they pivot their strategy to port BeOS directly onto Apple's hardware.
```mermaid flowchart TD accTitle: Alternative History OS and Browser Mergers accDescr: A flowchart showing how BeOS, Apple, and Telenor's Opera browser merged to create the Blink browser on yellow Banana Boxes. subgraph BeInc ["Be Incorporated"] A["BeOS (Multi-threaded OS)"] end subgraph Apple ["Apple Computer"] B["Struggling Hardware Maker"] end subgraph Telenor ["Telenor (Norway)"] C["Opera Browser (Presto Engine)"] end A -->|"Ported & Acquired"| B B -->|"Banana Boxes"| D["Yellow Apple Computers"] C -->|"Acquired & Renamed"| E["BeLink (Blink) Browser"] D & E -->|"Combined Platform"| F["First-class competitor to Perfect Digital"] ```
[04:13:48](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=15228s) Banana Boxes and the Birth of Blink
Be Incorporated pitches their high-performance, protected-mode operating system to Apple. Desperate for a savior, Apple enthusiastically acquires Be Incorporated. They completely overhaul their product design, releasing a new line of computers that the press instantly dubs "banana boxes" because they are bright yellow. Up until this point, computers have only ever been gray or beige; the striking yellow design makes them an instant home design sensation.
The only thing the new BeOS-powered Apple computers lack is a native Grid browser. Apple tries to license Cello, but Perfect Digital has already locked it down. They turn to the NCSA, but Mosaic is open-source, limping along, and insufficient. Out of the blue, Apple contacts Telenor, the Norwegian telephone company. As Beattie tells it:
> “Telenor say you know this is funny we have a grid browser we've been working on here it's a thing we call opera and we're not quite sure what to do with it.”
Apple and Be Incorporated strike a deal to acquire Opera, including its Presto rendering engine and network stack. They rename the browser "BeLink" to match the BeOS branding, though autocorrect instantly and permanently dubs it "Blink." Supporting all the standard Grid protocols—Create, Update, Delete, Select, and Submit—and featuring a built-in WYSIWYG editor, Blink becomes a formidable, first-class competitor to Perfect Digital.
[04:15:38](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=15338s) The Search Problem and the Birth of Goggle
With these competing platforms, the Grid experiences an unprecedented explosion. Internet service providers offer dial-up access bundled with five megabytes of free Grid space. Because heavy JavaScript frameworks were never invented in this timeline, five megabytes is an enormous amount of storage, allowing users to publish vast amounts of content. However, because anyone can publish anything, the Grid quickly becomes cluttered with low-quality pages. The massive, unsolved problem of this era becomes discovery: how do users find high-quality content?
At Stanford, two PhD students, Sergey Page and Larry Brin, are working out of a garage on a search algorithm they call "BackRub." The algorithm determines a document's credibility by analyzing how many other pages link back to it. Sergey suggests renaming the search engine after a "googol"—the number 10 followed by 100 zeros—to represent the vast scale of the Grid. However, when they send someone to register the domain, autocorrect strikes again, and they end up registering `goggle.com`.
Goggle features a beautifully minimalist homepage in stark contrast to the ad-heavy portals of the era. The technology works flawlessly, but the founders face a major dilemma: they have absolutely no idea how to monetize a free, minimalist search engine. They strongly dislike the idea of running ads, leaving them searching for a viable business model.
- **Storage Efficiency:** 5MB of free space is incredibly generous because the timeline lacks bloated JavaScript frameworks. - **The BackRub Algorithm:** PageRank's equivalent, relying on backlinks to establish document authority. - **The Autocorrect Typo:** The search engine is registered as `goggle.com` instead of `google.com`.
[04:17:45](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=15465s) The Black Envelopes and the May 4th Event
The monetization problem is solved when Larry Page receives a call from Steve Jobs, who is secretly working on a major project at NeXT and wants to acquire Goggle's PageRank technology. While the exact financial details of the deal remain shrouded in mystery, the consequences shake the tech world.
In April 1999, while the rest of the world is gripped by Y2K millennium bug hysteria, Silicon Valley tech journalists arrive at their desks to find hand-delivered, mysterious black envelopes. Inside is a black printed card that reads: "Get ready for the next generation" on the front, and "Menlo Park amphitheater, 4th of May 1999" on the back.
Rumors run wild. Many assume it is a promotional stunt for a new *Star Wars* movie because of the "May the Fourth" date. However, when journalists contact Lucasfilm, the studio dismisses the idea entirely. Beattie jokes that Lucasfilm replied, “Don't be ridiculous why would anyone make a sequel to Star Wars just we are not gonna mess with perfection.”
[04:19:13](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=15553s) Steve Jobs Unveils the NextBook
On May 4, 1999, the Menlo Park amphitheater is packed. Steve Jobs takes the stage and delivers a characteristically captivating presentation about the Grid, digital publishing, and the social impact of technology. He then reaches behind the podium and pulls out a laptop called the "NextBook."
The crowd has never seen anything like it. It is less than an inch thick, machined from a single piece of lustrous, anodized black aluminum. It completely dispenses with legacy ports: there is no floppy disk drive, no CD-ROM drive, and no serial port. It features only two USB ports and a headphone jack. When the audience wonders how they are supposed to load software or connect devices, Jobs reveals his masterstroke.
On cue, two dozen Apple employees planted throughout the audience reach under their seats, pull out NextBooks, open the lids, and instantly begin playing a live, wireless video stream of Jobs' presentation. The audience is completely blown away; nobody has ever seen Wi-Fi or streaming video before, let alone on a laptop this portable. Journalists abandon their professional composure, clambering over seats just to get a glimpse of the machine.
- **NextBook Specifications:** 333 MHz ARM RISC processor, 64 MB of RAM, and a 5 GB flash drive. - **Operating System:** Runs the next-generation version of the NeXTSTEP operating system. - **Connectivity:** Features built-in wireless internet, shipping with a compact base station called the NextEnd.
[51:07](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3067s) The NeXT Book, the Millennium Hangover, and Nintendo’s Reality
Continuing the speculative alternate history of personal computing, Steve Jobs’ NeXT introduces the "NeXT Book." Designed for effortless connectivity, users simply plug it into a standard phone jack. It comes equipped with an internal CD-ROM drive and blankets the home with wireless networking, eliminating the need to sit tethered to a wall socket. NeXTSTEP ships with a brand-new "grid browser" called Nexus, whose technical heritage traces back directly to the original browser application created by Tim Berners-Lee on NeXTSTEP hardware a decade earlier. Nexus boasts unprecedented responsiveness, running the fastest HyperLisp interpreter ever built directly within the core operating system architecture, fully integrated with Goggle search technology to pull up queries across local folders, backups, emails, or remote grid servers at once.
The transition past midnight into the year 2000 arrives with little catastrophe: the missiles do not fire, the software world survives the Millennium bug, and everyone wakes up on New Year’s Day with an immense hangover to face an unrecognizable landscape of rival systems. The ecosystem is split: NeXT Books run Nexus; "banana boxes" (BeBoxes) surf using Blink (acquired from Norwegian telco Telenor); Perfect Digital markets Gen 95 with an engine descended from Thomas Bruce’s Cello browser; while Sun Microsystems clings to relevance by continuing to market NCSA Mosaic with Java support that nobody cares about.
Then, in December 2002, Nintendo breaks years of quiet following their acquisition of John Carmack, John Romero, Jim Clark, and Marc Andreessen. After an early hit with *Super Mario Quake World*, Nintendo ships a platform simply called "Reality." It realizes the immersive cyberspace envisioned in Neal Stephenson’s *Snow Crash* and William Gibson’s *Neuromancer*: Carmack and Romero handle the visualization, graphic algorithms, and interface; Andreessen writes the networking stack; and the Silicon Graphics pedigree supplies the high-performance 3D rendering pipeline. Virtual reality takes over global communications.
```mermaid flowchart TD accTitle: Alternate Computing Ecosystem circa 2002 accDescr: Mapping hardware platforms and software stacks in Dylan Beattie's alternate history timeline.
subgraph Corporate ["The Alternate Landscape"] direction TB NXT["NeXT Corporation"] -->|ships| NB["NeXT Book (NeXTSTEP)"] NB -->|runs| NEX["Nexus Browser + HyperLisp"]
BE["Be Inc."] -->|ships| BB["BeBox Hardware"] BB -->|runs| BLK["Blink Browser (ex-Telenor)"]
NIN["Nintendo"] -->|funds Carmack, Romero, Clark & Andreessen| REAL["'Reality' 3D Metaverse (Dec 2002)"] end ```
- **NeXT Book specs**: Built-in CD-ROM, native base-station wireless routing, embedded phone jack interface. - **Nexus search**: Instant, unified querying spanning local disks, archival backups, email archives, and remote network nodes via Goggle algorithms. - **Industry reactions**: Sun Microsystems heavily subsidizes Mosaic/Java promotions, facing widespread indifference from engineers who favor HyperLisp.
---
[54:09](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3249s) The Historical Forks: Kildall, Berners-Lee, and Language Syntax
Dylan Beattie shifts from the counterfactual narrative to inspect the real-world historical pivot points that made our actual timeline just as improbable. The dominance of Microsoft began on a single afternoon in 1981 when IBM went shopping for a microcomputer operating system. They initially visited Digital Research founder Gary Kildall to license CP/M for the original IBM PC. Kildall missed the meeting because he went flying in his private plane on a clear day—though alternate accounts suggest he disliked IBM's terms and simply walked away. Because Kildall was unavailable, IBM turned to Bill Gates and Microsoft, then a modest outfit of 10 to 15 people who were writing debuggers and language tools in Washington. Had Kildall signed the agreement, IBM’s PC revolution would have cemented Digital Research as the software hegemon instead of Microsoft.
```mermaid flowchart LR accTitle: The 1981 IBM OS Decision Fork accDescr: Flowchart contrasting the decision to visit Gary Kildall versus Bill Gates for the IBM PC operating system.
IBM["IBM PC Project (1981)"] --> Choice{"First Meeting"} Choice -->|"Gary Kildall (Digital Research)"| CP["Kildall out flying / rejects terms"] Choice -->|"Bill Gates (Microsoft)"| DOS["Signs OS deal; births modern Microsoft empire"] CP -.->|"What could have been"| CPMS["CP/M becomes ubiquitous personal computing standard"] ```
Even fundamental components like URLs were contingent on quick personal choices. In an archival interview snippet, Tim Berners-Lee reflects on whether he would change any architectural decisions in the World Wide Web:
> “It turns out really if you think about you don't need this knife slash I could have designed it to not have the session boy now that people know people all over the people on the radio are calling it backslash backslash means that everybody's people haven't they use that finger so much think of the amount of you know of print now that would have been sage if we wouldn't have sales if I just remove the double slash but there you go yeah and you can't it seems like a good idea at the time could have been different” — Tim Berners-Lee
Markup syntaxes faced similar forks. HTML adopted its angle-bracket convention because Berners-Lee drew upon SGML, but markup could have readily mimicked LaTeX (popular across Sun and academic workstations since the early 1970s) or Microsoft’s Rich Text Format (RTF), which was established by the late 1980s.
- **Gary Kildall**: Pioneer behind CP/M, whose missed meeting with IBM redirected operating system history to MS-DOS. - **URL syntax regret**: The `//` was added to signify an authoritative path starting from the top domain root, but proved redundant since addresses always required the `http:` scheme header. - **Markup alternatives**: SGML's tag paradigm won out over backslash-heavy LaTeX commands and curly-brace RTF formatting blocks.
---
[57:04](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3424s) Near-Misses: Viaweb, Netscape, Nintendo, and Excite
The alternate world’s use of HyperLisp was rooted in real engineering trends of the 1990s. Paul Graham and Robert Morris built Viaweb entirely on Common Lisp, establishing the first viable e-commerce platform and selling it to Yahoo to fund the creation of Y Combinator. Embedded Lisp variants already commanded enterprise software: AutoCAD shipped with AutoLISP, and Emacs ran Emacs Lisp. When Netscape recruited Brendan Eich, their opening mandate was to embed Scheme (a dialect of Lisp) into the browser. JavaScript only emerged because management mandated a rush delivery under fierce deadlines, demanding a curly-brace syntax that superficially resembled Sun’s C-like Java to avoid alienating mainstream programmers.
Parallel close calls defined the early hardware and business landscape: 1. **The id Software Nintendo Pitch**: John Carmack and John Romero successfully engineered smooth side-scrolling on PC hardware and ported *Super Mario Bros. 3* to the IBM PC overnight, shipping a floppy disk to Nintendo. Instead of offering jobs, Nintendo threatened catastrophic legal action because physical game cartridges represented their sole, impenetrable protection against PC piracy. 2. **Netscape’s Origins**: Marc Andreessen and Jim Clark held high-level discussions with Nintendo to design a proprietary online gaming infrastructure before pivoting to found Mosaic Communications (later Netscape). 3. **Cello and BeOS**: Thomas Bruce truly wrote Cello as a Windows-based browser while serving as legal librarian at Cornell Law School; BeOS was built by ex-Apple executives, and Apple CEO Gil Amelio came within inches of purchasing BeOS before pivoting back to NeXT, bringing Steve Jobs back into Apple. 4. **The Excite-Google Buyout**: In 1999, Larry Page and Sergey Brin offered to sell Google’s search algorithms to web portal Excite for $800,000 because they lacked an ad business model. Excite’s executive team declined, deciding Google was not worth the money.
Dylan Beattie synthesizes these near-misses into an overarching critique of modern tech development, cautioning software creators against paralyzing perfectionism:
> “So many of these systems that we use and we rely on every day are not there because somebody worked really really hard to find the best solution or to make the best decision or to find the best possible team or circumstances to work with they're there because people found something that was just good enough and they thought about what can we do with it what's gonna be next cuz you know we have this thing in our industry analysis paralysis where you get overwhelmed with choice you don't know what to do next” — Dylan Beattie
[01:01:05](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=3665s) The Contingent Web and Making Progress
Dylan Beattie brings his counterfactual journey through web history to a close by reflecting on the sheer accidental nature of modern computing foundations. He recalls how easily the industry could have pivoted down completely different paths—whether into an alternate universe where key pioneers went off to build an online gaming network instead of the web browser, or our own reality, where global digital infrastructure ended up powered by a programming language hastily cobbled together in just ten days under severe corporate marketing pressure from Sun Microsystems. Looking back at these pivotal turning points, Beattie argues that historical technology choices cannot simply be categorized as correct or flawed moves.
Instead, the reality of engineering history is pragmatic and messy: what matters at any given moment is merely finding a viable path forward. As Beattie observes, “Even if you don't get those decisions right there isn't really a right and wrong all there is is have we got enough to go on and and make progress and as you see in this talk we could have ended up making a very very different kind of progress.” While musing that the future might still take unexpected detours, he welcomes the audience back to our present reality, encouraging everyone to appreciate the everyday web browsers we take for granted—Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge—before concluding his exploration of the web that never was.
## Notable quotes > [00:06](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=6s) Don't worry about changing database providers or worry, but know that every company who used an ORM in case they needed to switch databases never actually did it. — Dylan Beattie
> [27:36](https://www.youtube.com/watch?v=8JOD1AQGqEg&t=1656s) What Gary Kildall has realized and IBM haven't is that if your flagship computer is made out of off-the-shelf parts that you bought from China and Singapore and Taiwan, you don't actually own anything. — Dylan Beattie
## Mentioned Alphabet, Amazon, Apple, Apple Safari, ARM RISC, ARPA, ARPANET, Banana Boxes, Baz Luhrmann, Be Incorporated, BeLink, BeOS, Bill Gates, Blink, Brendan Eich, Cello, CERN, Cornell Law School, CP/M, CP/M-86, Digital Research, DNS, Douglas Adams, Dylan Beattie, Elizabeth 'Jake' Feinler, Excite, Gary Kildall, GEM 95, GEM/3, Gil Amelio, Global Repository of Interlinked Documents (GRID), Goggle, Google Chrome, Grid Perfect, GridBrowser.app, HOSTS.TXT, HTML, HTML 4.01, HyperLisp, IBM, IPv4, James Clark, Java, JavaScript, Jim Clark, John Carmack, John Romero, Larry Page, LaTeX, Marc Andreessen, Microcosm, Microsoft, Microsoft Edge, Mosaic, Mozilla Firefox, MP/M-86, Multicosm PLC, National Center for Supercomputing Applications (NCSA), NCSA Mosaic, NeXT, NextBook, NextEnd, NeXTstation, NeXTSTEP, Nexus, Nintendo, Nintendo 64, Opera, Paul Graham, Paul Mockapetris, PC/AT, PerfectDigital, Presto, Reality, Robert Morris, SAFE (Secure Application Frame Encryption), Scheme, Sergey Brin, SGML, Silicon Graphics, SMTP, Standard Unique Resource Finder (SURF), Stanford Network Information Center (NIC), Steve Jobs, Sun Microsystems, Super Mario Bros. 3, TCP/IP, Telenor, The Beatles, Thomas Bruce, Thomas J. Watson, Tim Berners-Lee, University of Southampton, University of Southern California (USC), Viaweb, WordPerfect, WordPerfect Corporation, Y Combinator, Yahoo
## Video description The story of the web is a story about freedom. It's a story about information, about breaking down barriers, about creating new ways for people to communicate, to collaborate, and to share their ideas. It’s also a story that has as much do with marketing, money and meetings as it does with research and innovation. It’s a story of mediocre ideas that succeeded where brilliant ideas failed, a story of compromises, rushed deadlines and last-minute decisions. And it could so easily have been very, very different. What if IBM had hired Digital Research instead of Microsoft to develop the operating system for their first PC, way back in 1980? What if Marc Andreessen and Jim Clark had gone to work for Nintendo in 1993 and never founded Netscape? What if one of the team at CERN had said “Tim, won’t it sound a bit silly if everyone spends the next fifty years saying double-you-double-you-double-you all the time”?
In this talk, Dylan Beattie will explore alternative history of the world wide web - a web with no Microsoft, no Windows; no Firefox, no Google and no JavaScript. A software industry from another timeline, a world of platforms, protocols and programming languages that are unmistakably alien - and yet strangely familiar.
So strap in, hold tight, and join us as take you on a journey through... the web that never was.
NDC Conferences https://ndcsydney.com https://ndcconferences.com
[Source](https://www.youtube.com/watch?v=8JOD1AQGqEg)