Lisp had images from day one -> already in 1960. The feature of saving and restarting was already developed then. Yes, one can save all and restore it later. P

Lisp had images from day one -> already in 1960. The feature of saving and restarting was already developed then. Yes, one can save all and restore it later. Problems are then naturally: open files, network connections, native threads, ... those are usually not restored after load. The state of a network connection is not to be restored. Interlisp had also image-based development which is another step up: source code is managed and stored. Most Lisp systems nowadays save source code in files and can keep track of locations, etc. Thus the source code management feature is usually stronger in Smalltalk. Smalltalk usually also has a VM with machine-independent code, where Lisp systems often have machine-native code. Thus in Smalltalk one can transfer an image to a different machine architecture, where most Lisp systems only transfer images on the same machine architecture & operating system combination. The Java VM lacks this easy memory image feature.