3 ms·
> i just can't really think of a 2021 scenario for CL, legacy code aside I've been reading similar statements every years since I started programming in Lisp i
by kazinator 6y ago
> i just can't really think of a 2021 scenario for CL, legacy code aside
I've been reading similar statements every years since I started programming in Lisp in around 2000, and could easily find more of the same going back in Usenet archives and whatnot before that.
"Against the tide of Common Lisp" (Usenet, 1986): https://www.usenetarchives.com/view.php?id=net.lang.lisp&mid=PDEzMTFAd2VsbC5VVUNQPg https://www.usenetarchives.com/view.php?id=net.lang.lisp&mid...
"Considered Opinion: LISP is Terrible" (Usenet, 1983): https://www.usenetarchives.com/view.php?id=net.lang.lisp&mid=PDQ3M0B3YXRlbmcuVVVDUD4%3D https://www.usenetarchives.com/view.php?id=net.lang.lisp&mid...
Excerpt: "I have been attempting to evaluate LISP as a programming language for VLSI design, and after having read MANY LISP programs, I have come to the same set of conclusions about LISP as a programming environment. To make LISP usable, each particular interest group defines/modifies/extends LISP for its own purposes. The result is a set of islands of users, each with their own "flavour" of language, which they claim is the "one, true, and holy LISP. I like the LISP data structuring; As a programming language I rank it in the same class as APL: useful, highly unmaintainble, very hard to document, and VERY unportable."
- TornadoFlame 6y agoThank you, now it's worse than before! No really, i get your points (through you other answers too). I decided to just dive into CL, if you have some valuable resource, i would like to know!