Interlisp project: Restore Interlisp-D to usability on modern OSes
interlisp.org
interlisp.org
That's all very well until you want to put your code in source control.
Now, add the change.log file to the version control and you have a block-chain?
You might not have been one of the lucky few people to have access to the institutional hardware running Lisp during the golden age of Lisp you're referring to.
Er. no. My comment on HN when this came up 6 years ago: [1]
There were some good ideas in Interlisp, ones that could be revived for other languages. One was the ability to select a block of code and have it pulled out and made a separate function. This was a safe transformation. All necessary variables were made parameters. Not hard to do in LISP. More useful for C++ refactoring.
> paredit is only a shadow of what interlisp was: true structural editing
¹https://mail-index.netbsd.org/netbsd-bugs/2001/05/30/0003.ht...
InterLisp-D was great fun and I would enjoy having for nostalgia. That said, the modern Common Lisp ecosystem is awesome as is its community so I personally would not use InterLisp-D for large projects.
What we have is access to the source code for the D-machine emulator that Interlisp-D/Medley Common Lisp ran on in the 1980's.
The emulator was quite usable on 1980-s hardware - I worked for the company that sold it in the late 80s and early 90s.
We are still deciding stuff like what exact open source license to use, and how much priority to give to the two main goals:
* Historical - can it run old system dumps with important systems like NoteCards, LOOPS, LFG...
* Modernization - integration with host OS (clipboard, file system, networking), increasing memory space, adding Unicode