Hi Lethalman,

writing good code is a refinement of writing any code. Humans make errors and 
the result of these errors in a stable system should not be catastrophic. I 
tried running my calculations forked below the UI Process but this hung the 
image all the same. A big problem are unintentional loops. Smalltalk can work 
with fractions and some Morphs use these fraction and if they become large 
Smalltalk can take virtually ages to complete a calculation.

Edgar, losing the image was luckily just a one time experience which made me 
much more cautious. But I do run into the emergency evaluator from time to 
time which can come as a shock to a new user. Imagine a kernel panic on the 
first day with your bright new Mac.

Cheers, Torsten
>
> > The biggest drawback in Squeak is its instability. It is too easy to
> > crash and hang Squeak with hanging being easier. Its like Windows 3.0.
> > When I write a Python program and start it and find out there is an
> > infinite or nearly infinite loop I kill the program and change the
> > source. In Squeak it means using CMD-. and hoping I get a usable state
> > again without the loss of data. I have even corrupted my image by saving
> > at the wrong moment right before the crash. Crashing and hanging was my
> > first bad impression after seeing the sweets coloured UI back in 3.2 and
> > have been much more annoying than "non standard" look and feel whatever
> > "standard" might be.
>
> This depends on how you design your application. Take care to save the
> image before doing anything else, and keep an eye on loops... also you
> can fork instead of running tests in the UI process. You won't lose
> data if you write good code...
>
> > Cheers, Torsten
>
> Bye.