> Imagine trying to poke at an error stack trace resulting in the only editor you could use to fix it breaking with the only means of recovery going back (outsi

> Imagine trying to poke at an error stack trace resulting in the only editor you could use to fix it breaking with the only means of recovery going back (outside of the all-encompassing environment, mind you) to an older version. Imagine being able to go back to an older version, and then being able to re-play the log of actions you'd taken to just before you broke the editor. The Smalltalk changes log let's you do that! https://cuis-smalltalk.github.io/TheCuisBook/The-Change-Log.html https://cuis-smalltalk.github.io/TheCuisBook/The-Change-Log.... > sometimes irreversibly hose the entire system No, not "irreversibly". Not without the kind-of malicious intent that would deliberately delete and overwrite back-up files!