Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In every technical publication, and on this site too, people are always comparing OO languages to Smalltalk. My experience is in Java: is Smalltalk so important that I should study it?
Smalltalk was one of the earliest object-oriented (OO) languages (with others like Simula and Eiffel) and can be said to be extremely “pure” in an OO sense:
ints,booleans etc)for,while,ifetc). Sounds impossible but it’s true!It also pioneered some other, now common, stuff:
And there are other things connected with Smalltalk which didn’t really make it into the mainstream:
And it’s fair to say that the Java collections API and the apache-commons collections API are heavily influenced by Smalltalk.
I wouldn’t say that you should learn Smalltalk per se, but a familiarity with the fundamentals of these features (now present in many other languages) is surely advantageous to you.
Note that there are currently only 123 questions on here about the language, which was originally intended as an educational language (i.e. aimed at children) by its creator, Alan Kay. It is not particularly heavily used anymore. That’s not to say it isn’t used. JPMorgan, for example, has a large exotic derivatives risk-management system written in it.