3 ms·
> It is dangerously easy, when changing and reloading code at the REPL, to get an application into a state which could not have been reached by the code it is c
by outworlder 13y ago
> It is dangerously easy, when changing and reloading code at the REPL, to get an application into a state which could not have been reached by the code it is currently running.
This is the key point people some comments have been missing. Since you can evaluate code whenever you want, the running instance might become a frankenstein, containing code and data that shouldn't be around anymore.
I'd like to see the point of view of Smalltalk users (who develop against the images).
- pjmlp 13y agoI only used Smalltalk at the university back in the day, before Java was born and it was a very nice experience. All the talks about live editing is nothing more than recovering the workflows we already had in Smalltalk and Lisp machines. If you destroy the environment, just restart not a big deal. If you already saved the environment into the image, just rollback to the previous image snapshot, not a big deal specially nowadays that image based source control systems are available, like Monticello and Metacello.
- aerique 13y agoI develop Common Lisp the same way (against an image) and it only was a problem when I just started. Soon enough it becomes second nature to know which functions have been changed and / or knowing when it is time to start over with a fresh image. tl;dr it is not much of an issue