That seems to be a common misunderstanding.
Smalltalk implementations are usually 4 files:
-- the VM (like the J VM)
-- the image file (which you mention)
-- the sources file (consolidated source code for classes/methods/variables)
-- the changes file (actions since the source code was last consolidated)
The sources file and changes file are plain text.
https://github.com/Cuis-Smalltalk/Cuis7-0/tree/main/CuisImag...
So when someone says they corrupted the image file and lost all their work, it usually means they don't know that their work has been saved as re-playable actions.
https://cuis-smalltalk.github.io/TheCuisBook/The-Change-Log....
> Is this the best way to build applications? Almost assuredly not.
False premise.
That seems to be a common misunderstanding.
Smalltalk implementations are usually 4 files:
-- the VM (like the J VM)
-- the image file (which you mention)
-- the sources file (consolidated source code for classes/methods/variables)
-- the changes file (actions since the source code was last consolidated)
The sources file and changes file are plain text.
https://github.com/Cuis-Smalltalk/Cuis7-0/tree/main/CuisImag...
So when someone says they corrupted the image file and lost all their work, it usually means they don't know that their work has been saved as re-playable actions.
https://cuis-smalltalk.github.io/TheCuisBook/The-Change-Log....
> Is this the best way to build applications? Almost assuredly not.
False premise.