Squeak 6.1 Keeps the Live-Image Dream Running at 30

Four years after 6.0, Squeak has shipped version 6.1 — roughly 1,700 merged patches touching more than 9,000 methods, landing just as the project closes in on its 30th anniversary. On paper it's a maintenance release of a niche Smalltalk. In practice it's something rarer: proof that a fully live, image-based programming environment — the kind mainstream tooling keeps reinventing in fragments — is still being maintained, still bootable in your browser, and still doing things your IDE can't.

Some context for anyone who wasn't around in the 90s: Squeak is the open-source Smalltalk that Dan Ingalls, Alan Kay, and colleagues built at Apple in 1996, a direct descendant of the original Xerox PARC Smalltalk-80. It's the substrate the first versions of Scratch were written in, the home of the Etoys environment that shipped on the OLPC laptop, and the ancestor Pharo forked from in 2008. When you touch Squeak, you're touching the longest continuously-evolved object system in existence.

What 6.1 actually changes

The headline work is developer tooling. There's a new tree browser that shows system categories, classes, and message categories as one hierarchy with Monticello package integration, plus a sweeping drag-and-drop rework — you can now copy or move classes, methods, and categories between browser panes, or drop a class reference straight into the world to inspect it. Tree widgets across the image got type-to-filter, recursive find, and better keyboard navigation. Inspectors can now display custom fields and menu items contributed by the object being inspected — the object decides how it wants to be examined, which is a very Smalltalk idea that tools like Glamorous Toolkit later built an entire product around.

The debugger picks up two commands worth stealing for any language: "send until…" runs execution forward until an arbitrary condition holds inside nested message sends, and "run to here" now works into expressions inside blocks. There's also a bytecode-level view that lets you step through the VM instructions of a compiled method. Because Smalltalk's debugger operates on live objects in a running image — you can edit a method mid-stack-frame and resume — these aren't breakpoints bolted onto a post-mortem view. They're closer to a REPL that happens to have a call stack.

The rest is quality-of-life: high-DPI fixes across buttons, sliders, menus, and themes; kernel fixes around process simulation and unwinding; a rebuilt "Objectland" that reconstructs the 2003 "Worlds of Squeak" demo tour; and, for the faithful, the return of BlobMorph after 18 years. Bundles cover macOS, Windows and Linux on both x64 and ARMv8, 32-bit builds, and a browser version running on SqueakJS. The release is dedicated to Vanessa Freudenberg (1972–2025), the longtime core contributor who created SqueakJS, the JavaScript VM that keeps Squeak images runnable on the web.

The uncomfortable part

The Hacker News thread on this release split exactly the way every Squeak thread has split for a decade: half the room describing the "wow moment" of a persistent live image, half complaining that the UI still looks pixelated and dated on modern displays. Both halves are right. The 6.1 high-DPI work is real but incremental, and Morphic's rendering stack shows its age next to Pharo's tooling or Glamorous Toolkit's Rust-based graphics layer. A volunteer team merging 1,700 patches over four years is a respectable pace for a heritage project; it is not the pace that closes a 20-year polish gap.

That's the honest read on where Squeak sits in 2026. The Smalltalk world quietly specialized: Pharo took the industrial lane, with consulting firms, a book ecosystem, and an annual release cadence; GemStone/S holds the transactional-persistence niche; Glamorous Toolkit turned the moldable-inspector idea into its own environment. Squeak became the preservation-and-education lane — the place where Etoys still runs, where the original Morphic lives, where a game written in 1996 still executes in the current image. That's not a failure. Somebody has to be the reference implementation of an idea, and Squeak is the reference implementation of live objects.

Why you'd actually open it

If you build developer tools, Squeak remains the cheapest way to calibrate your ambitions. Hot reload, edit-and-continue, notebook kernels, React Fast Refresh — each is a partial reconstruction of what an image-based system gives you wholesale: no build step, no restart, state that survives across sessions because the whole object graph is the persistence format. Spend an hour stepping through the debugger, changing a method mid-execution, and resuming, and you'll have a concrete benchmark for what "live" should mean in whatever you're building. The zero-commitment path is the SqueakJS build in a browser tab; the real thing is a ~100 MB bundle from squeak.org with the OpenSmalltalk VM included — a genuinely fast JIT VM that Pharo shares.

If you teach language design or OOP, 6.1 is the best classroom version yet: the restored painting-and-scripting tutorial, Objectland's guided demos, and the browsable-everything property (the compiler, the debugger, and the GUI are all ordinary classes you can read and edit) make it a syllabus in a box.

If you're maintaining a production Smalltalk system, the calculus is unchanged: new work belongs on Pharo or GemStone, where the libraries and the hiring pool are. Squeak 6.1's value to you is the shared VM work and the upstream fixes that flow across the family.

Should anyone else adopt it? No — and that's fine. Squeak 6.1 isn't a bid for relevance; it's a well-executed act of stewardship. The ideas it preserves keep leaking into the mainstream a decade at a time, and the leak rate says the source material still matters. There's a release party on September 2nd. Thirty years in, that's earned.