[squeak-dev] Smalltalk for small projects only?
stephane.ducasse at gmail.com
Sat Jan 28 19:19:03 UTC 2012
Managing 200 people is not equal to 20 times a team of 10.
You have to split in teams and each one will work on its own project, synchronized…..
I think that this has nothing to do with language. May be if you have interfaces and component like structure
it may help you.
On Jan 28, 2012, at 5:12 PM, James Robertson wrote:
> I'd say that the biggest driver is process, not language. Using version control tools and sane build process, the image is utterly irrelevant
> On Jan 28, 2012, at 10:46 AM, Janko Mivšek wrote:
>> Hi guys,
>> Ralph Johnson in his InfoQ interview made an interesting observation:
>> 2:55 minute: "Smalltalk made an fundamental error ... image ... you can
>> build something with 4-5 people what 50 people can build in Java, but if
>> you take 200 people in Java ... it is really designed for small systems
>> ... "
>> Are we because of the image really destined for relatively small
>> projects and small systems (of Java 50 people project size)?
>> Are we really not able to scale to bigger projects/systems because of that?
>> Ok, there are few exceptions of course (JPMorgan, OOCL, ..), but still...
>>  http://www.infoq.com/interviews/johnson-armstrong-oop
>> Best regards
>> Janko Mivšek
>> Smalltalk Web Application Server
> James Robertson
> jarober at gmail.com
More information about the Squeak-dev