Imagine having a REPL to your complete OS, not the just the basic CLI that most systems have.
There are a few videos of those days showing up the systems.
My experience with Oberon, lead me to track down how Wirth learned about such systems.
Additionally, I got to learn Smalltalk in the form of VisualWorks before Java was known to the world.
So I extrapolate my experience to how it might have felt back then and find it sad we are still trying rediscover it.
No kidding. I knew at least one guy who hosed a product launch by doing that. You even have to restart your development instance from time to time to make sure that your application state remains consistent. I've been scared to try, but I suspect that you could live-patch a server though if you were systematic about it and tested the patch ahead of time.
There are ways around that. Stuart Sierra uses a scheme wherein the entire application is treated as a value, which can be re-generated on the fly. Of course, that's not terribly different in practice from restarting the whole environment, but it's faster and more convenient.
http://thinkrelevance.com/blog/2013/06/04/clojure-workflow-r...
There are technologies deigned to enable live updates. VisualWorks Smalltalk had one, though it was not widely used. There are real time OS that can update the kernel without going down.
Ruby and Python borrow a lot from Lisp, including the REPL, but some of the most popular applications of those languages barely take advantage of it. Why?
[0] I'll stipulate that you might want to be very conservative about doing this with a production system.