Smalltalk’s Browser: Unbeatable, Yet Not Enough

The four-pane System Browser has been the dominant programming interface in Smalltalk for forty years. Its longevity stems from how well it provides structural context—showing a method within its class, alongside related classes. But the real friction in Smalltalk development isn't the browser itself; it's the lack of composition between the surrounding tools (debuggers, inspectors, playgrounds, message browsers). These tools coexist without integrating smoothly, making it hard to track a thread of investigation across multiple navigation steps. The post identifies four recurring IDE problems: 'Frankenstein tools' that accumulate features without coherent redesign, 'hermit tools' that don't share context, 'alien tools' that clash with OS conventions, and a 'saturated environment' (Pharo 14 ships ~10,750 classes vs. 223 in Smalltalk-80). The proposed direction isn't a better browser, but a workspace that treats the programmer's investigation as a navigable graph of related tools.