Skip to content

Languages / Smalltalk

Smalltalk

A pure object-oriented language known for its simplicity and live programming environment.

Learning and tools

Documentation, practical learning and development tools.

All Smalltalk resources →
Development and analysis environment

Glamorous Toolkit

Glamorous Toolkit is a Pharo-based Smalltalk development environment for exploring and explaining software and data. It combines live programming with contextual tools, visualizations and an integrated book of examples. Start with a…

Explore project →
Software and data analysis platform

Moose

Moose is a Pharo Smalltalk platform for software and data analysis. It provides models, importers, queries and visual tools for exploring systems and their structure. Start with the Modular Moose installation guide and first analysis…

Explore project →
Web framework

Seaside

Seaside is a Smalltalk framework for web applications built from reusable components. It uses programmatic HTML generation and callback-based request handling, allowing application behaviour to be expressed in Smalltalk objects and…

Explore project →

Current & upcoming events

All language events →

No current or upcoming events listed. Explore past events or suggest one.

Follow Smalltalk jobs with Atom → Get updates in your feed reader.

No jobs listed right now.

There are still resources and organizations to explore. Browse all jobs.

The Rise and Fall of Commercial Smalltalk

r/programming subreddit · Published June 3, 2020

Commercial Smalltalk vendors exited or downsized in the late 1990s and early 2000s as enterprise customers migrated to Java and other free runtimes, according to accounts from ParcPlace, Digitalk, and IBM alumni. The article argues that…

The Rise and Fall of Commercial Smalltalk

Allen Wirfs-Brock's blog · Published June 2, 2020

Commercial Smalltalk adoption collapsed after 1996 as major vendors exited the enterprise tools market and new Smalltalk application development largely stopped. Allen Wirfs-Brock attributes this shift to enterprise customers redirecting…

About Smalltalk and its ecosystem

Smalltalk is an object-oriented, dynamically typed programming language developed in the 1970s by Alan Kay, Dan Ingalls, and others at Xerox PARC. Known for its pure object-oriented model, Smalltalk treats everything, from numbers to classes, as objects. This uniform approach to programming encourages a highly consistent and intuitive style of coding.

Smalltalk's interactive development environment, including tools like the image-based virtual machine, allows for rapid prototyping and live editing, making it a popular choice for exploratory programming and research. It introduced many foundational concepts in object-oriented programming (OOP) such as message passing, which has influenced later languages like Python, Ruby, and Objective-C.

Though Smalltalk is not as commonly used in modern software development, it remains a key part of the history of object-oriented programming and is still used in certain niches, particularly for educational purposes and legacy systems. Its emphasis on simplicity, purity in object-oriented design, and its powerful development environment make it a fascinating language for those interested in the origins and principles of OOP.

Smalltalk: The Productivity Multiplier Finance Won't Talk About

When a major investment bank's derivatives trading system operates for over two decades with a development team representing less than 1% of total IT staff, it's not an accident. When that system consistently beats competitors to market by months on new financial products, it's not luck. Financial institutions don't deploy mission-critical trading systems on whims, and they don't maintain unconventional technology stacks for sentiment. The continued operation of Smalltalk platforms, handling billions in daily transactions across banking, energy trading, and specialized manufacturing, suggests something about total cost of ownership that the industry doesn't discuss publicly.

Energy trading platforms in Europe, built and maintained by teams of under a dozen developers, handle multi-country power exchange operations that competitors need 50+ engineers to manage. Custom ERP systems for specialized industries get deployed in less time than it takes to implement commercial solutions. When a 500-employee company builds complete custom ERP with 3-5 developers over three years, something about the development model is materially different. These aren't marketing claims; they're observable deployments where the team sizes seem impossible for the system complexity they're managing.

In 2025, Smalltalk jobs exist at major financial institutions, energy companies, and industrial operations, rarely posted publicly, mostly through direct referrals. The developer pool is aging, ecosystem is fragmented, hiring velocity is slow. But institutions in regulated industries continue maintaining these systems through disruption cycles that killed Java applets, Flash, and dozens of "modern" platforms. Not because Smalltalk is better. Because some organizations care more about incident rates than hiring friction. Beyond-tabs documents this not because Smalltalk is the future, but because the systems using it refuse to become the past. When banks still run trading systems on it, energy companies still build exchanges with it, the pattern becomes undeniable: every prediction of Smalltalk's death becomes another decade of production operation.

Suggest a project or resource

Share a useful Smalltalk project or resource.

Suggest a project →Suggest a resource →