That live image model dominated the conversation. People kept coming back to the same point: Smalltalk still teaches something most mainstream stacks hide, namely that an application can be a malleable object space rather than a pile of files plus startup code plus serialization glue. The strongest practical claim was not nostalgia. It was that image-based systems make state, inspection, and direct manipulation much cheaper. You can click through a running UI, inspect the object behind a button, patch behavior in place, and keep going. Several comments connected that to modern pain points like brittle initialization, repeated boilerplate for persistence, and the awkward split between runtime state and code artifacts that developers and AI tools both have to manage today.
A second theme was lineage. People pushed back on casual claims that Smalltalk alone explains later languages.
JavaScript was described more accurately as a mix of Smalltalk,
Self, and
Scheme ideas, with Self carrying much of the weight for the prototype model and Morphic itself tracing back to Self before landing in Squeak.
Ruby was another recurring example of a language whose approachable surface still carries a lot of Smalltalk DNA.
The mood was warm toward the ideas and cooler toward the current product experience. Squeak won praise as a mind-expanding system and as a still-remarkable environment for introspection. It also drew familiar complaints that the UI can feel old, deployment is awkward, and polished high-DPI support arrived later than it should have. A few people pointed newcomers toward
Pharo,
Glamorous Toolkit,
Cuis, Amber, SmallJS, and
SqueakJS depending on whether they care most about tooling, vector graphics, browser delivery, or easier adoption. The bottom line was blunt: the core Smalltalk ideas still look ahead of most modern tooling, but Squeak itself remains easier to admire than to drop into a mainstream workflow.
squeak.org