Hi Michael, S, Michael Haupt piše:
I think this is a post that clearly illustrates the big problem with smalltalk. The very fact that is compared with Java and Java survives.
Yes, that 4-5 people can do what 50 Java people are needed is both a blessing and a curse :)
I wanted to ask this earlier: is there actual evidence for this, or is it just boasting?
I think we need to ask Ralph to clarify that. But IMHO his main point is scaling from 50 to 200 ...
Blessing because of productivity, curse because we are not able to scale beyond one highly connected development group. We don't have project management practices and tools, while Java guys have because they need them from the start.
I'm not so sure the people at those Smalltalk firms building software for banks et al. have no project management. Boasting? ;-)
As I said in first post, there are few exceptions. But they all have their dev. process developed internally, while there are no common agreed and used development processes in Smalltalk as there are in enterprise Java development. Even more funny is that many (like Agile/Extreme programming) actually comes from that Smalltalk project "exceptions"... Best regards Janko