Measurements of early Smalltalk-80 implementations [Krasner 1983] indicate 20% to 70% of runtime spent garbage collecting.
Baden  proposes such a scheme for Smalltalk-80, which was implemented by Miranda .
However, two exceptions to this observation are the detailed account by Knuth of using a logbook to document all the errors he encountered over a 10-year development period working on TeX  and a logbook of the development efforts of a team implementing the Smalltalk-80
virtual machine .
The slightly subterranean but highly-regarded Smalltalk-80
software environment is for the development of tailor-made applications.
A cookbook for using the model-view-controller user interface in Smalltalk-80
MVC, which first appeared in the Apple Lisa personal computer, inspired many of the modern window and mouse-based interfaces.
Pane-based window systems have been successfully employed in a variety of different development environments such as Object Master  and Smalltalk-80
Object-oriented approaches to the software lifecycle using the Smalltalk-80
system as a CASE toolkit.
Of particular importance is that the test Member (obj, c) in Object Pascal or obj isKindOf: c in Smalltalk-80
responds true if obj is a member of class c or of any subclass of class c.
When the group started development work in 1983, there was a conflict between functional specifications (which clearly indicated that Smalltalk-80
was the preferred development environment), and the requirements for reliability and maintainability (which clearly indicated a well-proven software engineering environment based on a traditional programming language).
Her leadership of research and development teams was instrumental in the design and implementation of the Smalltalk-80