The computer systems running this LISP code had 4k of memory. There are a few subroutines (e.g. APUSH, FPUSH, CAR, CDR, etc.) but the inner loop looks pretty mu

The computer systems running this LISP code had 4k of memory. There are a few subroutines (e.g. APUSH, FPUSH, CAR, CDR, etc.) but the inner loop looks pretty much like a tightly coded state machine. I suspect most of the FORTRAN statements will compile to single instructions (on some architectures). FORTRAN level subroutine/function calls would use a stack and chew up memory. My PDP-8/f System was a small machine with a paper tape reader/punch on the teletype. Running the multi-pass FORTRAN compiler, linker, and library code paper tapes (including intermediate tapes) could take all day. I usually just hand-patched the final binary paper tape (using a small plastic holder and a 1-hole punch). The fact that I could run LISP and interact "on the fly" was an amazing advance. Later, when I worked for Unimation trying to computer-control industrial robots I got a Data General NOVA. Unfortunately I didn't have a FORTRAN compiler. All the robot work was done in hex machine code. Oh, if I only had a LISP!