updates vs. images -- limiting squeak to code

David T. Lewis lewis at mail.msen.com
Sat Oct 15 12:32:40 UTC 2005


On Sat, Oct 15, 2005 at 01:51:53PM +1000, Jonathan Kelly wrote:
> It's this very impression I had of sqeak that's holding me back from 
> saying, "Yeah, I want to use smalltalk". It seems to me that part of the 
> problem is that an image doesn't contain code, it's infected by it. I 
> will admit I probably haven't got into the headspace yet, if there is a 
> headspace, and there's obviously a lot I don't know, but I'm finding 
> less and less reason to think using smalltalk for my next project (and 
> it's a large project) is a good idea, if obviously very intelligent 
> people have difficulty managing code and staying current. Maybe "staying 
> current" is just another not so important mind set, but it's the one I 
> have (and almost certainly one the client has) ... :)

If "large project" means "three or more developers making lots
of stuff", then you should probably wait until you have some more
personal experience before using Squeak for this. If "large project"
means "complex system being developed by one or two smart people",
you will be very happy that you used Squeak. But I would think
you'll want to get some experience with it before taking on
something big with a budget and a delivery timeline.

You would probably get a wide variety of opinions on this, but
that's my $0.02. My own personal experience involves managing
large groups (non-Squeak, Roman Legion approach, spend enough
time and money and you eventually get large quantities of stuff),
and individual development in Squeak as a hobby. I have no
personal experience with managing a multiple-person Squeak
project, so YMMV.

Dave




More information about the Squeak-dev mailing list