4 ms·
What I find fascinating is less the balancing and structural editing, but that these old lisps _strongly_ embraced the absence of source files. The environment
by dleslie 6y ago
What I find fascinating is less the balancing and structural editing, but that these old lisps _strongly_ embraced the absence of source files. The environment was being edited, and not some text documents.
- galaxyLogic 6y agoThis is how Smalltalk is and was. Source-code is there but mostly for the purpose of restoring changes from the file change.log in case the "image" crashed. Now, add the change.log file to the version control and you have a block-chain?
- dleslie 6y agoAye, the thing is... I just haven't "clicked" with the ergonomics of Smalltalk systems. The language isn't too appealing, for starters; if feels too much like I'm using reverse polish notation, or a stack-based programming language. ;)
- cabalamat 6y ago> The environment was being edited, and not some text documents. That's all very well until you want to put your code in source control.
- dleslie 6y agoI don't see why the environment itself couldn't be adapted to have modern revision control.
- eschaton 6y agoThis is in fact exactly how modern Smalltalk systems interact with source control.
- pjmlp 6y agoWhich Smalltalk environments and SQL databases have tackled already for a couple of decades.
- varjag 6y agoWell, some older Lisps not only did support files, but also file versioning on operating systems allowing for that. You still have provisions for that in ANSI Common Lisp spec.