Smalltalk's Real Legacy — MVC and the GUI

smalltalk1-4 covered the image and the class browser — genuinely unfamiliar ideas to most programmers today. This chapter covers the opposite kind of legacy: two ideas from the exact same era and place that became so completely normal, they're now almost invisible.

Inventing MVC — Model-View-Controller

Trygve Reenskaug, working within the Smalltalk-80 environment at Xerox PARC as a visiting researcher, designed the Model-View-Controller pattern to solve a real, concrete problem: how should a live, directly-manipulable Smalltalk object (smalltalk1-4's own image model) be displayed on screen and respond to user input, without tangling the object's own actual data and logic together with the code drawing it or handling clicks?

Model — the actual data, logic, and state, a live Smalltalk object. View — how that model gets displayed on screen. Controller — handles user input and translates it into changes on the Model. Worth dwelling on given smalltalk1-3's own uniform-object philosophy: even this separation is achieved entirely through Smalltalk's own ordinary object and message mechanism — not a special framework bolted on top of the language, but the same single mechanism doing everything else in the system too.

MVC's Afterlife — Still Named Everywhere

react1, angular1, vue1, and svelte1 all still use "MVC" or a direct descendant term — MVVM, or "component-based" architectures that still separate state, view, and logic — as inherited vocabulary. Most web developers using these terms today have never heard of Reenskaug or Smalltalk-80 at all, working with a fifty-year-old pattern's own name without knowing where it came from.

Worth being precise rather than sweeping: modern frontend frameworks aren't literally implementing Reenskaug's original Smalltalk-80 MVC exactly as designed — django1's, rails1's, and laravel1's own MVC framing are structurally closer to the original server-side pattern than most client-side JavaScript frameworks are. But the underlying conceptual split — separate the data, the display, and the input-handling — is the direct, genuinely traceable inheritance, regardless of how loosely or tightly any given modern framework maps onto Reenskaug's own original three-part division.

Xerox PARC and the Graphical User Interface Itself

Beyond MVC as a software pattern, PARC's own research — much of it happening in the same building, same era, and same Learning Research Group culture that produced Smalltalk — pioneered the graphical user interface itself: the mouse, overlapping windows, icons, menus. The entire visual vocabulary of "using a computer" that's now so completely normal it's effectively invisible.

Why the GUI and Smalltalk Are the Same Story

This ties directly back to smalltalk1-2's own Dynabook vision: a computer meant to be directly, visually manipulable by a child needs a visual interface, not a command line. The GUI wasn't a separate PARC project that happened to exist alongside Smalltalk — it was a genuinely necessary part of realizing the same underlying vision, and Smalltalk's own live image (smalltalk1-4) was frequently the actual environment being displayed and manipulated through these new GUI concepts in the first place.

Reflection Questions