Smalltalk traditionally breaks this source vs. executable state dichotomy by using a single memory image where everything is an editable object, including the c

Smalltalk traditionally breaks this source vs. executable state dichotomy by using a single memory image where everything is an editable object, including the classes that contain the code. For persistence, the image is simply stored and reloaded in its entirety.