Pharo 14
- ID
- 39805
- Status
- summarized
- Published
- 26 Oct 2026, 7:15 PM
- Fetched
- 27 Oct 2026, 9:07 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://pharo.org/news/2026-10-26-Pharo14Release.html
- Source URL
- https://hnrss.org/best
Summary
- Score
- 4.5
- Created
- 27 Oct 2026, 9:09 AM
- Tags
- Audience
- developersvibe_coders
What happened
Pharo 14 shipped, the first release under a new cadence that moves the project from spring (March–May) to fall (September–November) windows. Tooling work dominates: a new Mission Control, Pulse replacing Spotter, a rewritten Settings Browser, a reworked Method Browser, and Epicea plus ProfStef folded into NewTools on the Spec stack. The VM side adds RISC-V JIT support, unified frame/stack management, direct old-space allocation with GC changes, and expanded command-line tooling (testing, a debugger, Sindarin scripts).
Why it matters
Two details change decisions rather than just announcing a version: the release window now lands in fall, so anyone pinning Pharo for a course, internal tool, or product should plan upgrades against Sep–Nov instead of spring; and RISC-V JIT support plus the command-line debugger/testing work make Pharo newly plausible on non-x86/ARM CI runners and in headless scripted pipelines, which is where most teams would actually touch it.
Discussion angle
Pharo's pitch is editing and debugging live objects in a running production image with no compile/deploy step — worth comparing honestly against hot-reload and live-repatch workflows in Node, Python, or Erlang: what does an image-based environment actually buy you, and what does it cost when you need to hand a system to a team that has never used one?