Earlier quoted context omitted.
I agree that it is a language worth understanding. However the OO model of Ruby is identical. Without the drawbacks of being an image based language. So I'd suggest learning that instead. For those who don't know what I am talking about, there are several families of languages where the state of your program is kept within an image. The upside of this is that you can integrate everything together in a really neat way…
> I agree that it is a language worth understanding. However the OO model of Ruby is identical. Smalltalk is much more than the OO model.
On the other hand if your intent is to learn about its collection classes, what MVC looked like in its original inspiration, and so on, then you should learn Smalltalk.
There is more to learn than any of us has time for. If you know what you hope to get out of learning something like X, then you should pick the most convenient X around to learn it.