In graduate school, I would have been hard pressed to store my current/typical Smalltalk image, let alone move it from place to place, so think about disk space too. Overall, we probably still benefit from the efficiency that limited resources demanded. With very little effort, Dolphin produced deployed executables of 1 (with work) to 4 (being sloppy about it) MB. There is of course a fair amount of support code in the form of DLLs, both from Windows and the VM, but the part that one had to deliver for a hot fix was very manageable. So far, the one "deployed executable" that I have from Pharo is about 60 MB image+changes. In fairness, I was happy to get it working (I use it pretty much every day), and have not attempted any tricks to reduce its size. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Marcus Denker [marcus.denker@inria.fr] Sent: Wednesday, October 19, 2011 2:49 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] IS Smalltalk Source also an object? On Oct 18, 2011, at 9:31 PM, Nicolas Cellier wrote:
2011/10/18 Schwab,Wilhelm K <bschwab@anest.ufl.edu>:
Maybe I've played too much football without a helmet or did too much C programming,
Yes, and yes, that's why you missed Eliot's answer ;) http://permalink.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/55024
Nicolas
but I see two questions popping out of this: (1) is source an object in Smalltalk;
So yes, I have been convinced that it is an object (as even a string is an object). (yet, we should think if with the resources we have today as opposed to 1978, can't we do even better? I always wonder how smalltalk would look like if they would have had 4GB of RAM instead of 256KB...) Marcus -- Marcus Denker -- http://marcusdenker.de