On 12/01/2010 06:49 PM, [email protected] wrote:
I'm afraid we're missing something essential on this: what problem Pharo
(or more generally Smalltalk) addresses better in the enterprise than
other technologies?
Cesar,
Part of the answer to this question should come from a look at the
existing enterprise customers that are basing their business on Smalltalk.
The Smalltalk success stories (at the enterprise level) come from
solving problems that are very difficult to solve in the first place.
Looking at some of GemStone's customers there are two common
characteristics:
- large complex problems
- problems whose domain is rapidly changing
The large problems have to be broken down into pieces that are small
enough for a small team of people to attack effectively and the work of
these small teams has to be integrated to address the larger problem.
This plays into the strength of Smalltalk in that Smalltalk code (and
developers) can thrive in an environment where the code base is
inconsistent/fluid ...
For problems whose domain is rapidly changing it is a requirement that
the _architecture_ of the system be able to migrate over time. As
business rules change the architecture of the system has to evolve.
Again the requirement of having a malleable code base where
functionality can migrate and the architecture can evolve play into the
strengths of Smalltalk...
My $0.02...
Dale
