3 ms·
For me, that was my "I'm getting out of here before I break it irreversibly" moment while working through some introductory tutorial ~20 years ago; I've never t
by mkl 2mo ago
For me, that was my "I'm getting out of here before I break it irreversibly" moment while working through some introductory tutorial ~20 years ago; I've never touched Smalltalk again. I can't understand why being bespoke and unreproducible would be a desirable thing for software.
(Yes, clearly I don't "get it". Happy to hear explanations.)
- igouy 2mo agoIt's unfortunate but understandable that the stuff which is most different from other programming environments grabs attention and the basic stuff is hardly mentioned. > break it irreversibly Nope. "Cuis-Smalltalk records any action occurring in the environment: the code you edit in the System Browser, the code you execute in a Workspace. Therefore, in the event of a Cuis-Smalltalk crash you can restore unsaved changes when you launch the same Cuis-Smalltalk image again." https://drcuis.github.io/TheCuisBook/The-Change-Log.html https://drcuis.github.io/TheCuisBook/The-Change-Log.html > bespoke and unreproducible So there have been all manner of ways to save code changes as plain text in files (or other formats in databases). https://drcuis.github.io/TheCuisBook/The-Change-Set.html https://drcuis.github.io/TheCuisBook/The-Change-Set.html https://drcuis.github.io/TheCuisBook/The-Package.html https://drcuis.github.io/TheCuisBook/The-Package.html