Smalltalk and the Dream of Programming as a Living Medium
Smalltalk joined an object-oriented language, a graphical environment and a vision of personal computing into one unusually integrated system at Xerox PARC.
Smalltalk began with a vision larger than language syntax
Alan Kay’s history of Smalltalk places the language inside a broader 1960s and 1970s research tradition concerned with interactive computing, simulation, graphics, and human-computer symbiosis.[1] The goal was not simply to produce a better notation for professional programmers. It was to explore computing as a personal medium.
At Xerox PARC, the Learning Research Group pursued that vision through hardware, user interfaces, educational experiments, and the evolving Smalltalk system.
Objects were conceived as communicating entities
Smalltalk’s object model emphasized messages between objects rather than direct manipulation of internal representation. In Kay’s account, this drew inspiration from simulation languages and from thinking about software components as small, semi-independent computers.[1]
Encapsulation was part of the communication model
An object’s state belonged to the object; other parts of the system asked it to perform operations by sending messages. This made software design less about globally visible data structures and more about networks of cooperating components.
Everything in the environment reinforced the model
Smalltalk’s influence came partly from consistency. Numbers, collections, windows, text, and user-created objects participated in the same general message-oriented world, making the system feel conceptually unified rather than assembled from unrelated mechanisms.
The Alto made the environment tangible
Smalltalk developed alongside Xerox PARC’s Alto, a personal workstation with a bitmap display and pointing-device interface. The language, graphical environment, and machine reinforced one another. Smalltalk programs could create windows, graphics, editors, animations, and interactive tools that made the abstract object model visible on screen.[3][4]
This integration is why Smalltalk history overlaps with the history of graphical user interfaces rather than belonging only to programming-language history.
The development environment blurred code and running system
Smalltalk encouraged programmers to inspect live objects, browse classes, edit methods, and immediately observe the effect on a running system. Programming became an activity inside the computational world being modified rather than a separate phase that always ended in a rebuild.
Image-based development preserved a whole world
Smalltalk systems popularized the idea of saving an image containing objects, code, and development state. That model differed sharply from source files plus a separate executable and influenced later interactive environments.
Tools were written in the language they supported
Browsers, inspectors, debuggers, and workspace tools were themselves Smalltalk objects. This reflexive quality made the environment extensible and taught generations of programmers that development tools could be part of the same programmable system.
Smalltalk-72, -76 and -80 mark an evolving research program
Smalltalk was not created once. The system evolved through major versions during the 1970s, with changes to syntax, object behavior, inheritance, virtual-machine implementation, and the development environment. Computer History Museum preservation work documents this long evolution rather than treating Smalltalk-80 as the whole story.[3]
Smalltalk-80 later became the most widely disseminated version and helped carry PARC ideas into universities and commercial systems.
Object-oriented programming acquired a powerful exemplar
Classes and objects existed before Smalltalk, notably in Simula, but Smalltalk made object orientation the organizing principle of an entire interactive environment. Its influence can be seen in later languages, frameworks, graphical systems, and design vocabularies.
The word ‘object-oriented’ would eventually encompass systems very different from Smalltalk, but the PARC model remained a reference point for message passing, encapsulation, late binding, and interactive development.
The graphical legacy reached beyond Xerox
Apple’s history intersects directly with PARC. The Computer History Museum’s Apple timeline records the 1979 visit in which Steve Jobs and colleagues saw PARC’s graphical work, including Smalltalk demonstrations, and carried GUI ideas into Apple projects.[5]
That transfer is sometimes simplified into a single visit, but Smalltalk’s deeper legacy was a research ecosystem showing that language, interface, and personal hardware could be designed together.
Why Smalltalk remains a model of computational intimacy
Smalltalk asks a question that still feels modern: what if programming were not mainly the production of files for a compiler, but direct manipulation of a living system? Its browsers, inspectors, objects, graphics, and message sends made software feel immediate and explorable.
That sensibility reappears in notebooks, live coding, visual development tools, browser developer consoles, and modern environments that shorten the feedback loop between intention and behavior. Smalltalk’s enduring contribution is therefore both technical and experiential.[1][2]
Works Cited
- 01
- 02Computer History Museum — Oral History of Alan Kay archive.computerhistory.org
- 03Computer History Museum — Introducing the Smalltalk Zoo computerhistory.org
- 04Computer History Museum archive — The Evolution of Smalltalk smalltalkzoo.computerhistory.org
- 05Computer History Museum — Apple Timeline (1979 Xerox PARC visit) computerhistory.org
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead