2 ms·

Fun fact: this is very similar to how Smalltalk works. Instead of storing source code as text on disk, it only stores the compiled representation as a frozen VM

Fun fact: this is very similar to how Smalltalk works. Instead of storing source code as text on disk, it only stores the compiled representation as a frozen VM. Using introspection, you can still find all of the live classes/methods/variables. Is this the best way to build applications? Almost assuredly not. But it does make for an interesting learning environment, which seems in line with what this project is, too.

igouy 2y ago
> only stores the compiled representation 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/CuisImage 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.html https://cuis-smalltalk.github.io/TheCuisBook/The-Change-Log.... > Is this the best way to build applications? Almost assuredly not. False premise.