March 5, 2026
Fractals vs fossils
Smalltalk's Browser: Unbeatable, yet Not Enough
A 40-year-old tool sparks love, eye-rolls, and a fight over what's missing
TLDR: The classic Smalltalk browser still shines for context, but the author says tool integration is the real gap. Comments split between “obsolete relic,” “it already works,” and “bring back the magic,” turning a niche IDE debate into a lively fight over the soul of programming.
Smalltalk’s famous four-pane code browser just set off a retro tech brawl. In his piece, Esteban Lorenzano says the old-school browser is still brilliant for context, but the real issue is that the surrounding tools don’t play nicely together. Cue the comments section turning into a reunion show and a roast. One fan waxed poetic, calling code browsing a fractal where tools need to flow together, while another waved a nostalgia flag for Whisker, a sideways browser that fit widescreen monitors like a glove. The counterpunch? A skeptic rolled in with “didn’t this go obsolete?” energy, wondering why Smalltalk keeps popping up like it’s the internet’s favorite zombie. Then a practical voice flat-out said: the tools already integrate, what’s the problem? Meanwhile, a romantic take crowned Smalltalk “an open book” and begged the world to rediscover its magic, citing the legendary F-script Anywhere as proof. Between fractal philosophy, widescreen hacks, and monthly Smalltalk resurrection memes, the thread reads like a family dinner where everyone insists they’re right. Whether you think the browser is timeless or tired, the drama is delicious: is the icon perfect, or is it stuck in the past without a band to play with?
Key Points
- •Smalltalk pioneered IDE features such as live inspection, fast feedback loops, and strong navigation decades ago.
- •The four-pane System Browser remains the dominant programming surface in most Smalltalk IDEs and has persisted for about forty years.
- •Modern tools like Pharo and Glamorous Toolkit’s Coder retain the same underlying four-pane browser metaphor despite different UIs.
- •Proposed message-flow navigation approaches rarely become default because they tend to sacrifice the structural context developers need.
- •The author argues the deeper UX issue is not the browser itself but poor composition between surrounding tools, emphasizing methods’ placement within classes and packages.