[igouy]

And that was about me being tired of the bogus Smalltalk's so fragile meme.

So how would we explore fundamental changes that break the debugger? Would the dumbest workable thing be create subclasses without changing the originals?

I have come across someone who genuinely seemed to think that making copies of just the image was a viable approach to version control. Their project failed badly; and they were absolutely convinced the problem had been Smalltalk, when the problem was not understanding how they could use Smalltalk.

[cess11]

I didn't say it was fragile.

[igouy]

> corrupts the entire image

Epitome of fragility.

A different story if you'd gone-on to explain recovery.

[cess11]

Maybe find someone who actually thinks this environment is fragile and bring this hang-up there?