Hell Is Other REPLs
I guess I never &quot;got it&quot;.<p>What CL development I&#x27;ve done, it was pretty much &quot;reload it and rerun it&quot; in terms of a development cycle. Mind, these were not large programs. But there was enough global, shared state that needed to be reset that, most of the time, a simple tweak to a function wasn&#x27;t enough to right whatever wrong was involved. And the reloads weren&#x27;t arduous anyway.<p>Sure, for &quot;little work&quot;, &quot;local work&quot;, tweaking a routine, doing simple tests and such in the listener. It was fine. Very quick turn around.<p>But when fixing something that was larger in scope? Reload it, rerun it.<p>I also never &quot;got&quot; the restart and condition systems in CL. Part of this is simply my background, today mostly being in Java where production debugging is doing archaeological digs on deep stack traces.<p>I get restarts in interactive systems. But my systems were not interactive. They were server based systems, processing zillions of requests. I never saw the utility of a restart on a headless system. I could not imagine a connection stuck in a restart just waiting for me to fix it, debug it, correct it, continue it, or abort it. In contrast to just logging the torrid details of the failure and path to it and using the information in a post mortem.<p>Do folks get 3am phone calls to open up a server and dig through restarts? That never made any sense to me. On paper, it sounds great, I just never saw any realistic way it would ever apply in any of the work that I did.<p>Are there times it would have been nice to log in to a server, tweak a piece of code, and let it continue on? Changing the tires of a car on the road? Sure. Occasionally.<p>Mind, that could just be habitual. Since to me it was a novelty, and one unavailable to me, perhaps I simply don&#x27;t miss it. Yea, it makes sense when hacking deep space probes. But a generic remote web service type of application in production? To me, not so much.<p>The idea of hot patching a server is amazing and frightening at the same time. How was the patch tested, do you commit it to VC first, before cut and pasting the DEFUN in to the listener, etc.<p>The same applies to Smalltalk. The idea of sending out an application that faults and drops the user in to a restart and debugger. What can they do with that? Call me up and talk them through it? I&#x27;d much rather them send me the log file with a post mortem I could use. I&#x27;m sure ST has ways of capturing stack traces in log files, but, casually, nobody talks about it.<p>So, I&#x27;d love to hear stories about what I&#x27;m missing. What applications folks were doing that were leveraging these aspects of the CL experience. How they manifest on system with any transaction volume (you know, a few trx per second). How one uses restarts in a web shopping cart in production.<p>Make no mistake, in Java, with the applications servers, turn arounds can be pretty long. But, similarly, with code structure, units tests, etc. turn around can be very fast. Make a tweak to the code base, repeatedly run an isolated unit test until it works, then run the larger suite to see what else you broke. That can be quite fast. Not &quot;interactive&quot;, but...fast. &quot;Close enough&quot;.