Inzischen haben sich einige interessante Antworten angesammelt. Nicht nur, dass man sich einen Eindruck verschaffen kann, in was für Projekten Smalltalk eingesetzt wird, sondern es gibt auch eine ganze Menge Meinungen zu Smalltalk zu lesen. Einige Fundstücke:
A tightly integrated environment complete with refactoring, the most highly expressive language I’ve ever come across, true Object Oriented programming, true reflection, minimal keywords, helpful community, etc.
The cons end up being things like:
- smaller pool of experienced developers
- ‘special’ deployment considerations
- lack of a standard libraries (each vendor has slightly different base libraries) which contributes to the lack of ‘polished libraries’
As a programming environment, the reflexive and agile nature of Smalltalk allows us to prototype rapidly, then to implement adaptive tools.
Smalltalk allows me to be agile, productive, my systems are maintainable regardless of all changes of business climate in recent years.
Two drawbacks of Smalltalk are that there are not a lot of preprepared components around (comparing to the other development environments) and that interfacing with others is somehow hard and therefore rarely used.
The main benefit I find is the debugging support, the ‘low ceremony’ of dynamic typing and the expressiveness of Smalltalk syntax and Seaside. On the downside it takes a while to get used to the image and maintaining it effectively; using a source code repository helps though.
I’m one to two orders of magnitude more productive writing web apps with Seaside than with our regular .net frameworks.
Es lohnt sich, alle Antworten zu lesen, der Überblick ist sehr interessant, und brandaktuell!