Smalltalk
A pioneering object-oriented programming language and development environment developed at Xerox PARC in the 1970s. Smalltalk has had a profound influence on core software engineering concepts including graphical user interfaces and object-oriented programming.
Core Facts
Timeline (last 90 days)
In Smalltalk, integers, booleans, code blocks, classes themselves and even nil are all objects, and method calls uniformly use message-sending syntax.
Smalltalk systems persist classes, methods, object instances and development tools in a binary file called an "image", and on startup restore a runtime snapshot containing the state of all objects.
Pharo is an open-source Smalltalk environment.
Smalltalk's image model makes it difficult to directly apply modern engineering practices such as version control, multi-person collaboration, and build and release, because Git deals with text files rather than object graphs.
The Language Server Protocol (LSP) assumes static text files and codebases that can be analyzed offline, which conflicts with Smalltalk's model in which "code exists only in a live object graph".
Pulsar's appearance at ESUG 2026 shows that the Smalltalk community is still investing resources in maintaining and updating its own core tools, rather than relying only on a few long-standing environments.
To assess Pulsar's fate, what is worth watching is its subsequent open-source strategy, the images/runtimes it supports, and whether it can genuinely improve day-to-day coding and debugging experience while preserving Smalltalk's dynamic features.
A Smalltalk system usually consists of two parts: a virtual machine (VM) written in a low-level language such as C that handles memory management and bytecode execution, and an image running on top of it that contains the compiler and all the tools.
ESUG is the annual conference of the European Smalltalk User Group, the most important gathering in the Smalltalk ecosystem, and has historically been the occasion for new projects, new libraries, and new tools to be shown publicly for the first time.
In traditional Smalltalk, a program is the entire running object graph serialized and saved as a binary file (image), and code modifications act directly on the running objects, rather than writing files first and then compiling and loading them.
2 more timeline events
All Facts (13)
Object-oriented programming was born in the 1960s with the Simula language and was popularized by Alan Kay in Smalltalk.
70%UnverifiedIn Smalltalk, integers, booleans, code blocks, classes themselves and even nil are all objects, and method calls uniformly use message-sending syntax.
50%UnverifiedPharo is an open-source Smalltalk environment.
50%UnverifiedSmalltalk systems persist classes, methods, object instances and development tools in a binary file called an "image", and on startup restore a runtime snapshot containing the state of all objects.
50%UnverifiedESUG is the annual conference of the European Smalltalk User Group, the most important gathering in the Smalltalk ecosystem, and has historically been the occasion for new projects, new libraries, and new tools to be shown publicly for the first time.
50%UnverifiedSmalltalk's image model makes it difficult to directly apply modern engineering practices such as version control, multi-person collaboration, and build and release, because Git deals with text files rather than object graphs.
50%UnverifiedThe Language Server Protocol (LSP) assumes static text files and codebases that can be analyzed offline, which conflicts with Smalltalk's model in which "code exists only in a live object graph".
50%UnverifiedA Smalltalk system usually consists of two parts: a virtual machine (VM) written in a low-level language such as C that handles memory management and bytecode execution, and an image running on top of it that contains the compiler and all the tools.
50%UnverifiedPulsar's appearance at ESUG 2026 shows that the Smalltalk community is still investing resources in maintaining and updating its own core tools, rather than relying only on a few long-standing environments.
50%UnverifiedTo assess Pulsar's fate, what is worth watching is its subsequent open-source strategy, the images/runtimes it supports, and whether it can genuinely improve day-to-day coding and debugging experience while preserving Smalltalk's dynamic features.
50%UnverifiedIn traditional Smalltalk, a program is the entire running object graph serialized and saved as a binary file (image), and code modifications act directly on the running objects, rather than writing files first and then compiling and loading them.
50%UnverifiedSmalltalk/Squeak is one of the earliest systematic practitioners of the live programming philosophy, predating concepts such as hot reload and REPL-driven development by decades.
50%UnverifiedSqueak is an open-source, cross-platform Smalltalk implementation whose virtual machine and development environment are themselves largely written in Smalltalk (self-implementation).
50%