In memory of Eric Binnion

Bill Joy: vi, the C Shell and BSD’s Free Software Legacy

Bill Joy at Davos in 2003, photograph by Joi Ito, cropped

Sticker 004 · Bill Joy · Back to the album card · Leggi in italiano

Bill Joy helped change how people worked with Unix: editing text on screen, interacting with commands, and making Berkeley’s software usable by a wider community. His name is associated with vi, the C shell and the early BSD distributions. In 1982, he became one of the co-founders of Sun Microsystems.

The fourth entry in the Outstanding Programmers Sticker Album explores a practical kind of excellence: building tools that help other people build software. You do not need to write code to appreciate the difference between an awkward tool and one that becomes a reliable extension of your work.

Who is Bill Joy, and why does he matter?

Joy’s Computer History Museum oral history traces his education at Michigan and Berkeley and his move to Sun. It is a first-person source for his decisions and experience, best read alongside technical documents and accounts by other participants.

Unix came from the Bell Labs work of Ken Thompson and Dennis Ritchie. Berkeley added its own research and tools. In Marshall Kirk McKusick’s history of BSD, Chuck Haley shares credit for work on ex, which drew on George Coulouris’s em editor. Recognising these predecessors and collaborators gives a more useful picture of innovation than a lone-inventor story.

Vi: bringing text editing onto the screen

A text editor modifies files, including programs, configuration and documents. Line-oriented editors required commands to act on particular lines. Vi offered an interactive view of the text. The introduction by William Joy and Mark Horton, in the edition annotated by Gunnar Ritter, explains the connection between what the terminal displays and the file being edited.

Vi’s distinctive interface separates inserting text from issuing commands. In insert mode, a letter becomes part of your text; in normal mode, it can request an action. This takes practice because the meaning of a key depends on the current mode. Once learned, it allows many changes without constantly moving your hands away from the keyboard.

As a teaching example, dw combines deletion with movement to the next word, while 3w repeats a movement three times. These are user commands, not quotations from Joy’s source code. The important idea is composition: a small vocabulary can express many operations without a separate command for every situation.

Vi emerged during the 1970s. Later editors that share its interaction model have their own authors and implementations. Preserving an interface does not make Joy the author of every program that implements it.

Termcap: keeping hardware differences outside the editor

Different terminals needed different control sequences to move a cursor or redraw a screen. Termcap described terminal capabilities so an application could consult device information instead of embedding every hardware variation throughout its own logic.

Think of it as an adapter between a program’s intention and the terminal’s behaviour. This separation makes each side easier to reason about. Our editorial interpretation is that recognising such boundaries helps explain why a tool can remain useful beyond the hardware that first motivated it.

The C shell: improving everyday interaction

A shell accepts commands and launches programs. The C shell, or csh, is another major Joy contribution, discussed in his museum interview. It is not the C programming language, although parts of its syntax resemble C.

The value of an interactive shell becomes clear through repetitive work: finding an earlier command, shortening a frequently used instruction, or controlling work started from a terminal. Small reductions in friction add up over a working day. Interactive convenience and scripting requirements are different questions, however; an influential shell need not be the best choice for every task.

BSD and virtual memory were collective achievements

BSD stands for Berkeley Software Distribution. McKusick describes Joy’s development and distribution work, but also identifies Özalp Babaoğlu’s work on virtual memory for the VAX and Joy’s subsequent help with integration and debugging. Giving one person credit for the whole system would erase essential contributions.

Virtual memory lets an operating system organise programs’ address spaces using mechanisms involving physical memory and disk. It does not create unlimited resources: retrieving data from slower storage has a cost. This is the less visible engineering that makes visible applications practical.

From Berkeley to Sun Microsystems

Berkeley Engineering’s profile places Joy’s move to Sun in 1982. Bringing Unix into industrial workstations meant connecting research to hardware, networks and users outside the university. This part of his career involved technical direction and collaboration as well as writing programs.

An authentic ex/vi excerpt, with careful attribution

The file ex.h in heirloom-ex-vi, revision 34c196f credits Mark Horton and Bill Joy and records later changes by Gunnar Ritter. The following three definitions are reproduced without adaptation. They are authentic code from the ex/vi lineage as preserved in the consulted port, not an assertion that this file exactly matches the first 1970s version.

#define	CTRL(c)	((c) & 037)
#define	NL	CTRL('j')
#define	CR	CTRL('m')

The CTRL macro performs a bitwise operation. 037 is octal notation for 31; applying the mask to ASCII values keeps the lowest five bits. The next two definitions derive newline and carriage-return codes from j and m. These few lines connect the editor to character encodings and terminal control.

Attribution limit: the file documents project authorship and later revisions, but does not establish who wrote each of these three lines. We have not verified an excerpt with demonstrably exclusive individual authorship by Joy. The excerpt is unchanged from the cited file; the explanation is ours.

The file header carries redistribution conditions for the University of California Regents’ code, Caldera notices and conditions for Ritter’s changes. We preserve the full file notice below. The Traditional Vi project also distinguishes its port from the 2002 release of restrictions on ancient Unix code. A single blanket licence would not describe every historical BSD component.

This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed or owned by Caldera International, Inc.

Copyright notices and conditions of the quoted file
/*
 * This code contains changes by
 *      Gunnar Ritter, Freiburg i. Br., Germany, 2002. All rights reserved.
 *
 * Conditions 1, 2, and 4 and the no-warranty notice below apply
 * to these changes.
 *
 *
 * Copyright (c) 1980, 1993
 * 	The Regents of the University of California.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 * 	This product includes software developed by the University of
 * 	California, Berkeley and its contributors.
 * 4. Neither the name of the University nor the names of its contributors
 *    may be used to endorse or promote products derived from this software
 *    without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 *
 * Copyright(C) Caldera International Inc. 2001-2002. All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *   Redistributions of source code and documentation must retain the
 *    above copyright notice, this list of conditions and the following
 *    disclaimer.
 *   Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 *   All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *      This product includes software developed or owned by Caldera
 *      International, Inc.
 *   Neither the name of Caldera International, Inc. nor the names of
 *    other contributors may be used to endorse or promote products
 *    derived from this software without specific prior written permission.
 *
 * USE OF THE SOFTWARE PROVIDED FOR UNDER THIS LICENSE BY CALDERA
 * INTERNATIONAL, INC. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
 * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED. IN NO EVENT SHALL CALDERA INTERNATIONAL, INC. BE
 * LIABLE FOR ANY DIRECT, INDIRECT INCIDENTAL, SPECIAL, EXEMPLARY, OR
 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
 * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
 * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
 * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
 * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 *	from ex.h	7.7.1.1 (Berkeley) 8/12/86
 *
 *	Sccsid @(#)ex.h	1.57 (gritter) 8/6/05
 */

The free-software legacy requires a licence distinction

FreeBSD’s official Explaining BSD notes that historical distributions containing AT&T source required a Unix source licence. Academic access to code did not automatically grant unrestricted redistribution. The later transition to freely redistributable releases and modern BSD systems involved many further contributors.

Joy belongs in this album because of the technical foundations and working practices he helped establish. Looking closely at licences makes that legacy clearer: a community can exchange and improve tools before every obstacle to free redistribution has been removed.

What this sticker teaches

Our reading highlights three qualities: attention to everyday tools, practical responses to constraints, and care in integration. These are observations about engineering work rather than claims about Joy’s personality. An efficient editor must work on the available terminals; a distribution must be usable by people beyond its original developers.

Previous sticker: Douglas McIlroy and Unix pipes · Explore the complete album.

Sources and image credit

Primary and project sources: Bill Joy’s Computer History Museum oral history (2011); Marshall Kirk McKusick’s BSD history (1999); Joy and Horton’s vi guide, annotated edition (2002); ex.h source and licence notices; FreeBSD documentation; Berkeley Engineering. Editorial verification: 19 November 2026.

Image: Bill Joy at Davos, 2003. Photograph by Joi Ito; crop uploaded by SqueakBox, via Wikimedia Commons, licensed CC BY 2.0. Existing crop used without further editorial alteration.

Nominate a programmer

Do you know a programmer, well known or overlooked, who made an outstanding contribution? Describe the project and provide verifiable sources. Editors review every nomination before publication; submitting this form does not automatically add anyone to the album. Your name and contact details are optional; please avoid sensitive personal information.

← Back

Thank you for your response. ✨







Leave a comment

Your email address will not be published. Required fields are marked *