The four-pane System Browser has shaped Smalltalk development for forty years. It’s still brilliant at providing context. But the real problem may not be the browser itself—it may be the lack of composition between the tools that surround it.
Smalltalk’s Browser: Unbeatable, Yet Not Enough
Smalltalk is one of those systems that looks “old” until you realize it was often first. Many things we take for granted in modern IDEs—live inspection, tight feedback loops, powerful navigation—were part of Smalltalk culture decades ago.
And yet the daily experience of working in Smalltalk is still dominated by a metaphor that has barely changed in forty years: the four-pane System Browser. It’s brilliant at providing context. It’s also the start of a wider UX problem.
Take a look at this screenshot from Smalltalk-80—you can clearly see the System Browser in action:
Smalltalk-80 system browser and companions
The System Browser (also called the class browser) is meant to explore the class structure of the system. In practice, it’s the main programming surface in most Smalltalk IDEs.
Here are two modern incarnations—different eras, different UI styles, same underlying metaphor:
The system browser in Pharo
"Coder", the system browser in Glamorous Toolkit
... continue reading