Well, for one thing, there are a lot of production Smalltalk applications out there still. Some of them are quite good. There are also a lot of bad implementations out there, but that is true for any language. (Sturgeon's Law!)
The Smalltalk Refactoring browser is still very impressive, though it has now been surpassed by Eclipse. It predated Eclipse by some years, however. There are other tools that were developed under Smalltalk that have yet to be adopted by other programming communities. Also, the performance of the fastest Smalltalk VMs has been very good for many years now. Bad architecture will swamp even programs in C or assembly. I'd hazard a guess that you were dealing with that.
But you are correct that there are serious problems with many of the Smalltalk implementations. None of these had anything to do with the language, the tools, or the VMs. Rather, there was a legacy of "ivory tower" mentality. Instead of doing very necessary but unglamorous things like polishing the GUI framework (and eliminating race conditions) implementors preferred to do cool things like create new garbage collection options.
Smalltalk suffered because community input was neglected, because the same community fostered an elitist culture, because marketing went for an more closed "boutique" approach, and because implementations weren't polished to true professional standards. It would behoove Ruby, Python, and others to heed these lessons. (And I'd note that they've done many things right.)
The Smalltalk Refactoring browser is still very impressive, though it has now been surpassed by Eclipse. It predated Eclipse by some years, however. There are other tools that were developed under Smalltalk that have yet to be adopted by other programming communities. Also, the performance of the fastest Smalltalk VMs has been very good for many years now. Bad architecture will swamp even programs in C or assembly. I'd hazard a guess that you were dealing with that.
But you are correct that there are serious problems with many of the Smalltalk implementations. None of these had anything to do with the language, the tools, or the VMs. Rather, there was a legacy of "ivory tower" mentality. Instead of doing very necessary but unglamorous things like polishing the GUI framework (and eliminating race conditions) implementors preferred to do cool things like create new garbage collection options.
Smalltalk suffered because community input was neglected, because the same community fostered an elitist culture, because marketing went for an more closed "boutique" approach, and because implementations weren't polished to true professional standards. It would behoove Ruby, Python, and others to heed these lessons. (And I'd note that they've done many things right.)