Softwareopen-sourcepharosmalltalkprogramming-languages
Pharo 14 Brings Smalltalk-Style Live Coding to the Command Line and RISC-V, After 978 Pull Requests
The open-source Pharo environment shipped version 14 on October 26, 2026, months late, with a command-line debugger, a RISC-V JIT, rebuilt tools and a new fall release schedule.
Pharo’s About page describes it as “a dynamic, pure, reflective object-oriented programming language in the tradition of Smalltalk.” The release notes put the pitch more bluntly: “No constructors, no types declaration, no interfaces, no primitive types,” and “a full syntax fitting in one postcard!”
The idea is a live system. “Even in production environments, you will never be stuck in compiling and deploying steps again!” The debugger is the showpiece, letting you “restart the execution of methods, create methods on the fly, and much more.”
Version 14 pushes that environment outward. The team kept “expanding Pharo’s command-line capabilities (command-line testing, a command-line debugger, and Sindarin script tooling),” which matters for anyone who wants Pharo in a CI pipeline instead of only in its own windowed world.
The virtual machine got the deeper work. The notes list “RISC-V JIT support, expanding platform coverage and future-proofing VM development,” unified frames and stack management, and “direct old-space allocation and numerous GC and allocation improvements.”
The tools got rebuilt too: “Introduction of Mission Control,” “Introduction of Pulse (Spotter replacement),” a reworked Method Browser and a rewritten Settings Browser that is now the default.
It shipped late, and the team said so in June. “You may have noticed that our usual April–May release did not happen this year,” the timeline post began. “There is not much mystery: we got very ambitious about what we wanted to include.” The release notes make the slip permanent: “we have moved our release schedule from spring (March–May) to fall (September–November).”
The count is “978 Pull Requests integrated just in the Pharo repository,” with 616 issues closed since Pharo 13. One line in the announcement still reads “with more than [X] contributors for the last revision of the platform,” a template placeholder nobody filled in before it went live.
A command-line debugger is the kind of feature that can bring a niche environment into ordinary build systems, where more developers will run into it. With the release moved to fall, Pharo 15 lands on that calendar next. The next number to watch is the one in the brackets.