2 ms·
I consider the 1958 Lisp to be dead. The Lisp family's longevity doesn't stem from maintaining legacy code from 1960, but because it actually embodies attractiv
by kazinator 8y ago
I consider the 1958 Lisp to be dead. The Lisp family's longevity doesn't stem from maintaining legacy code from 1960, but because it actually embodies attractive concepts that continue to captivate new generations of coders, often not in connection to anything mundane, like a job.
- kazinator 8y agoNot ragging on Lisp here in any way, but it's been long since the original Lisp is has been viable. It continues to historic significance, and anything that calls itself Lisp still has cons, car, cdr, atom, lists ending in nil (which is a symbol) and such. In 1958, you had no macros, no lexical closures, no exception handling, no backquote, no objects or structures, no bignum integers, ... Whereas COBOL today is pretty much the same pile of stuff it was in 1960-something. It's not a vibrant language family with newer members. COBOL does not absorb new concepts. There are new, young people learning COBOL, but only in order to become maintainers of legacy systems: job security in banking, finance and government sectors. Maybe a few have a perverse curiosity: they want to know what is really behind the dirty five letter word. New people coming to a Lisp are coming for the Lisp itself. There aren't that many Lisp jobs involving new or legacy coding; new Lisp people learn and make new stuff from scratch. There is simply no comparison.