Home |
Embedded Files
Why Was WorldWideWeb Renamed Nexus?
WorldWideWeb was renamed Nexus to distinguish the first web browser from the World Wide Web itself. Tim Berners-Lee's explanation is specific: the application's name could be confused with the wider information space. Nexus gave the program a separate identity while the Web retained its name. [^1]
Berners-Lee developed the browser at CERN in 1990 on a NeXT computer. By the end of that year, a working browser and server demonstrated the proposed system. [^2]
The renaming story concerns the relationship between that first application and the larger project it helped people use. Understanding the story requires reading the early documents carefully, because their naming conventions were still taking shape.
One Name for a Program and a Project
The original proposal supplies an important piece of evidence. Dated November 12, 1990, and attributed to Tim Berners-Lee and Robert Cailliau, it is titled WorldWideWeb: Proposal for a HyperText Project. The joined name identified a project for connecting information, rather than being reserved exclusively for one application. [^3]
The proposal described a browser as a program through which someone could access hypertext. Servers supplied information, and links could lead between documents on different machines. This distinction was already present in the design: the browser was one component of a system involving documents, servers, and connections across computers. Giving the application the project's name made their relationship easy to express, but left the name open to more than one interpretation.
Berners-Lee later explained that the name World Wide Web emphasized the system's intended global reach and its decentralized structure. Information could be connected through a network of links, rather than having to fit into a single hierarchy. His naming explanation concerns the wider system and the kind of information structure he wanted to create. [^4]
Today, WorldWideWeb commonly identifies the original application, while World Wide Web identifies the wider system. Berners-Lee recommends three separate words for the latter.
That convention helps modern readers, but the November 1990 proposal shows why spacing alone cannot reliably identify the meaning of every early reference. The surrounding document matters.
What the Evidence Establishes About the Rename
Berners-Lee's own account explains the change as a way to separate the program from the information space. His stated reason directly addresses the ambiguity created by their shared name.
The timing is less precisely documented in that account. CERN's 2019 reconstruction team examined a Nexus version 2.02 executable bearing a 1994 copyright date. That supplies a dated surviving example of software using the new name. It does not, by itself, establish the day or year in which the renaming decision was made. [^5]
The choice of the replacement word is a separate question. His account explains why a different name was needed, but does not explain why Nexus was selected.
What the Browser Was Designed to Do
WorldWideWeb was designed as a browser and an editor. The preserved user guide describes a prototype that could access hypertext servers, files, and news. Its instructions say to open a linked document by double-clicking gray text; double-clicking ordinary text selected a word. Those controls placed navigation and text manipulation in the same working environment. [^6]
The authoring instructions describe creating documents and making links between them. They also explain a command that created a new document and linked to it at the same time. The application therefore offered tools for adding material to a collection as well as exploring material already there. [^7]
Imagine writing an overview of a research project and connecting a selected passage to supporting notes. The link gives a reader a route from the overview into the evidence or explanation behind it. Creating a further document could extend that route again. This is the practical relationship between reading and authorship that the browser-editor design made possible.
Editing had boundaries. The original instructions allowed changes to existing documents accessed as files, while information retrieved from remote databases could not normally be edited. They distinguished working with an editable document from merely retrieving information.
Berners-Lee also notes that the application browsed HTTP resources but edited only documents accessed as files, because HTTP PUT had not been implemented. That method can send a resource to a server, but the browser provided no such way to save changes back. [^1]
Why the Software Version Matters
WorldWideWeb developed over time, and descriptions of one version should not be applied automatically to every other version. The preserved change history records the switch from gray link highlighting to underlining on March 26, 1991. It also records editing failures in the 1993 version 1.0 alpha, followed by an entry for a forthcoming version 2.0 reporting that editing worked again. These entries document changing behavior, rather than a single unchanging feature set. [^8]
The same change history connects a file's editable status to its protection and the user's identity. These records help us read feature descriptions accurately: screenshots and instructions concern particular states of the software, and editing depended on both the version's functionality and the user's access to files.
The Web Beyond Its First Browser
The original application's dependence on NeXT computers limited who could use it. Nicola Pellow developed the Line Mode Browser at CERN for a much wider range of machines. CERN's 1991 software distribution included that browser, server software, and a library for developers, helping the system reach people without the original graphical application. [^2]
Mosaic followed in 1993, with versions that brought graphical browsing to PCs and Macintosh computers. These browsers widened access to the Web through different applications. Their history illustrates the difference between a browser application and the system it accesses.
The distinction also extends to the Internet. A browser is an application; the Web is an information space whose resources have addresses; the Internet supplies the underlying network infrastructure. W3C's explanation separates the Web from the Internet rather than treating them as interchangeable names. [^9]
The growing choice of browsers illustrates the practical importance of distinguishing the program from the Web. It does not establish the date or cause of the rename. For those questions, Berners-Lee's account and the surviving software records remain the relevant evidence.
Reading the Historical Evidence Today
CERN's 2019 WorldWideWeb reconstruction lets readers examine a recreation of the interface inside a contemporary browser. It provides access to the application's menus and interaction patterns without requiring an original NeXT machine. The reconstruction is a later implementation, and its website documents the rebuilding work. [^10]
Its accompanying guide demonstrates opening a target document, marking it, and making selected text in another document link to that target. This offers a concrete way to understand how writing and navigation could work together. The recreation illustrates the design; the preserved instructions and version records document historical behavior. [^11]
CERN's code investigation makes another useful distinction. Its team consulted surviving source code, an executable identified as an early WorldWideWeb version, and the later Nexus 2.02 executable. Comparing those materials helped the researchers understand changes in functionality. Their findings should be read as an examination of particular surviving versions. [^5]
Nexus gave the application a name of its own within a system already designed to support different browsers and servers. The early proposal, preserved software documentation, and later accounts explain that distinction while leaving the remaining gaps in the naming history visible.
Tim Berners-Lee, The WorldWideWeb browser, W3C. The creator's account of the rename, interface, and editing limits.
CERN, A short history of the Web. The browser's development and the expansion of access through other browsers.
Tim Berners-Lee and Robert Cailliau, WorldWideWeb: Proposal for a HyperText Project, November 12, 1990. Contemporary evidence of the project name and the browser-server design.
Tim Berners-Lee, Frequently asked questions, especially the sections on spelling and the name WWW. The creator's explanation of the wider system's name.
CERN's 2019 reconstruction project, Inside the Code. Examination of surviving WorldWideWeb and Nexus software.
Original WorldWideWeb documentation, WWW User guide. Instructions for the prototype's documented controls.
Original WorldWideWeb documentation, Making your own documents. Document creation, linking, and editing boundaries.
Preserved NeXT application documentation, Features and Bug Fixes, W3C. Changes in behavior across software versions.
W3C, What is the difference between the web and the internet?. Definitions of the network and information space.
CERN, 2019 WorldWideWeb Rebuild. The modern reconstruction and its documented purpose.
CERN's 2019 reconstruction project, The Browser. Instructions for exploring the recreated interface.
Related reading: The First Web Browser Was Also an Editor.
Legal Matters
This page is independently written and contains no affiliate links, sponsored content, paid placements, or compensated endorsements. TimsJam.com is an independent website and is not affiliated with, endorsed by, sponsored by, or officially connected with Sir Tim Berners-Lee, the WorldWideWeb Consortium (W3C), Inrupt, CERN, the Solid Project, or any other organization mentioned on this page.
For corrections, permissions, privacy requests, or accessibility assistance, use the contact form or call +1 (650) 427-9358. For details, see Legal, Privacy and Accessibility.
Disclosure: AI tools assist with research, summaries, drafting, and editorial review. Their use varies by article and stage of the writing process. Ardan Michael Blum writes, revises, and updates the content, shapes its arguments and interpretations, and makes the final editorial decisions.
Google Sites
Report abuse