ACM Home Page
Please provide us with feedback. Feedback
Why Smalltalk?
Full text PdfPdf (136 KB)
Source
Communications of the ACM archive
Volume 38 ,  Issue 10  (October 1995) table of contents
Special issue on object-oriented experiences and future trends
Pages: 105 - 107  
Year of Publication: 1995
ISSN:0001-0782
Author
Adele Goldberg  Chair and founder of ParcPlace Systems, Inc, Sunnyvale Calif.
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 72,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/226239.226260
What is a DOI?

ABSTRACT

Smalltalk is a single paradigm language with very simple semantics and syntax for specifying elements of a system and for describing system dynamics [1]. When the language is used to describe an application system, the developer extends Smalltalk, creating a domain-specific language by adding a new vocabulary of language elements while maintaining the same semantics and syntax. Using most Smalltalk systems, it is easy to invent one's own development environment through inclusion of new system parts in the library and extension of the development tools. Moreover, it is possible to make changes to the environment, and to applications written using the environment, while the system is executing. These system characteristics create a flexible and enjoyable software development experience.