Yeah, I guess there are strong such reasons why the Unixy model won over Smalltalk (and Lisp) when it comes to the basic O/S level. What I attribute more or le

Yeah, I guess there are strong such reasons why the Unixy model won over Smalltalk (and Lisp) when it comes to the basic O/S level. What I attribute more or less to "chance" (by which I basically just means the reasons are so multifarious that it's hard to say anything about them in general) is that Smalltalk didn't become more of a model for the desktop environments. The big desktop environments are still mostly coded in C-like languages, although I guess it's changing slowly, especially with people becoming used to dynamic languages from web programming. Of course, NeXTStep and OS X have a Smalltalk legacy, but they're not dynamic and interactive in the same way. Another point is that since Smalltalk can be almost totally O/S independent, your images can run identically across platforms, including the entire development interface. And the development interface isn't separate from the "user" interface. Regardless of Smalltalk's alleged death, the idea of having a system where you can interactively edit the source code of components is pretty radical, and will probably always be around. It's also kind of contrary to keeping source code proprietary, which might be an underrated reason for Smalltalk's unpopularity?