On Oct 10, 2011, at 8:24 PM, Schwab,Wilhelm K wrote:

> Andy Bower once compared an image to a "messy bedroom" - (paraphrasing the 
> rest), e.g. one that maybe does not look all that great, but the occupant 
> knows where to find everything.  The biggest problem I have with images is 
> that they start to work for me and I don't want to change them.
> 
> It seems to be a universal argument among Smalltalkers: save things in the 
> image vs. know exactly how to build the image and do so every day.  The 
> latter has the advantage of not requiring lots of archeology to discover what 
> makes something work.  One argument against saving images is that they can 
> get damaged over time.  I have had reasonable luck in avoiding ugliness.  In 
> part, I know that some things (e.g. running new FFI code) are dangerous and 
> can corrupt an image or just plain crash the vm.  So, I get things ready to 
> run the suspect code, save, and then run/exit/edit/save until I have 
> something that work.
> 
> Stef, I wish you luck in reaching your kernel and scripting language.  It 
> would be really nice if the system can still save images.
It will :)

> 
> Dolphin's licensing more or less requires that applications be deployed 
> differently than development images.  I have had success making a Pharo image 
> work as an end-user application, but it is a somewhat clunky process.  It 
> would be nice to have something that takes care of the details (saving the 
> image elsewhere, locking it, etc.) using a wizard interface.  Too many ideas, 
> too little time...

yes same here :)

> 
> Bill
> 
> 
> 
> ________________________________________
> From: [email protected] 
> [[email protected]] On Behalf Of Stéphane Ducasse 
> [[email protected]]
> Sent: Monday, October 10, 2011 1:54 PM
> To: [email protected]
> Subject: Re: [Pharo-project] OT: Dart
> 
> Indeed I always felt stupid :)
> But now I also want a mall kernel and scripting syntax (and a image one 
> demand only).
> So :)
> 
> Stef
> 
>> 
>> Note one sneaky thing: using an image as means of deployment:
>> http://www.infoq.com/news/2011/10/google-dart-language mentions "Dart
>> comes with tools to create an image of the heap of an application and
>> package it into an optimized format which can be loaded nearly
>> instantly, reminiscient of Smalltalk's image system."
>> 
>> Funny, given the number of arguments Smalltalkers have with people
>> over the use of images.
>> 
>> frank
>> 
>>> On 10 October 2011 14:43, Pavel Krivanek <[email protected]> wrote:
>>>> Hi,
>>>> 
>>>> Google published the first information about Dart:
>>>> http://www.dartlang.org/
>>>> 
>>>> Cheers,
>>>> -- Pavel
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Best regards,
>>> Igor Stasenko.
>>> 
>>> 
>> 
> 
> 
> 


Reply via email to