Kornel@artemissian LISP is pointer-heavy. When LISP and LISP machines were hot, RAM access took exactly 1 CPU cycle. Now it takes ~300 cycles. Maybe some purely-functional flavor could be made to work, but that's beyond my imagination.
The current state favors data-centric embarrassingly parallel programs with minimal pointer indirections.
All GNU social JP content and data are available under the