GitHub and Codeberg links on the site don't open for me. ("To protect your security, codeberg.org will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.") This is because of the use of frames:
>"Please don't assume Lisp is only useful for Animation and Graphics, AI, Bioinformatics, B2B and Ecommerce, Data Mining, EDA/Semiconductor applications, Expert Systems, Finance, Intelligent Agents, Knowledge Management, Mechanical CAD, Modeling and Simulation, Natural Language, Optimization, Research, Risk Analysis, Scheduling, Telecom, and Web Authoring just because these are the only things they happened to list."
>While in high school, he saw output from one of the guess the animal pseudo-artificial intelligence (AI) games then popular. He considered implementing a version of the program in BASIC, but once at the Massachusetts Institute of Technology (MIT), instead he implemented it in several dialects of Lisp, including Maclisp.
Kent Pitman's Lisp Eliza from MIT-AI's ITS History Project (sites.google.com)
While not Common Lisp I've always found it pretty cool that AutoCAD shipped with a Lisp, making the language technically a hugely deployed commercial success.
Were it not for early exposure to Autolisp I would not have appreciated Lisp or Lisp-based systems, like Emacs, the way that I did. I might've ended up whinging that they didn't use a mOdErN language like JavaScript.
Autolisp definitely sent me down the left-paren path.
The unfettered instrumental rationality of the techno-slob on full display. Bonus depravity-points if the multi-paragraph HN comments are also being outsourced to the Machine.
Depending on a corporation to do your programming (and burning half the planet in the process, pardon the hyperbole) is the very opposite end of the "hacker" ethos where Lisp stands. Very surprising to see this sort of comment on HN, of all places.
Kind of yes and kind of no. Not many reasons to use Common Lisp I agree, but the Lisp idea itself has still something to offer that couldn’t be found in other systems.
I’m comfortable to declare that are not macros the most powerful thing of Lisp, but the concept of an environment. Still in 2026 many languages now implement the concept of evaluating the code and make it immediately available but nothing is like Lisp.
Lower level programming languages today they all still requires compilation. Lisp is one of the few that I found having the possibility to eval code and its immediately usable and probably the only that really relies heavily on REPL driven development.
Env+REPL imo is the true power still far ahead of other languages. I can explore the memory of my program while my program is running, change the code and see the changes in real time.
The issue is that CL is old, and Clojure is so close to be perfect if it wasn’t for Java. Clojure replaces Java, not CL and this is its strength but also its weakness.
Can your LLM do that to a running system? Or will it have to restart the whole program to run the next iteration? Imagine you build something with long load-times.
Also, your Lisp will always behave exactly as you intended and hallucinate its way to weird destinations.
High level programming languages were conceived by humans and for humans. Will AIs in future better use their own languages, or maybe even output machine language directly?
_emacsomancer_|18 days ago
veqq|16 days ago
psychoslave|16 days ago
networked|16 days ago
testermelon|16 days ago
DonHopkins|15 days ago
>Kent Pitman
He left out Guessing Animals!
https://en.wikipedia.org/wiki/Kent_Pitman
>While in high school, he saw output from one of the guess the animal pseudo-artificial intelligence (AI) games then popular. He considered implementing a version of the program in BASIC, but once at the Massachusetts Institute of Technology (MIT), instead he implemented it in several dialects of Lisp, including Maclisp.
Kent Pitman's Lisp Eliza from MIT-AI's ITS History Project (sites.google.com)
https://news.ycombinator.com/item?id=39373567
https://sites.google.com/view/elizagen-org
https://climatejustice.social/@kentpitman/111236824217096297
https://web.archive.org/web/20131102031307/http://open.salon...
https://youtu.be/hHNDZnxiwlE?t=740
https://news.ycombinator.com/item?id=38402813
tmtvl|16 days ago
vindarel|15 days ago
coryrc|16 days ago
Fr0styMatt88|16 days ago
bitwize|16 days ago
Autolisp definitely sent me down the left-paren path.
pjmlp|16 days ago
Just like Gimp eventually added support to Python alongside Script-Fu.
Which end up reducing the interest to reach out to Lisp languages.
mck-|15 days ago
vindarel|15 days ago
bitwize|16 days ago
[deleted]
b00ty4breakfast|16 days ago
ChanderG|16 days ago
silcoon|16 days ago
I’m comfortable to declare that are not macros the most powerful thing of Lisp, but the concept of an environment. Still in 2026 many languages now implement the concept of evaluating the code and make it immediately available but nothing is like Lisp.
Lower level programming languages today they all still requires compilation. Lisp is one of the few that I found having the possibility to eval code and its immediately usable and probably the only that really relies heavily on REPL driven development.
Env+REPL imo is the true power still far ahead of other languages. I can explore the memory of my program while my program is running, change the code and see the changes in real time.
The issue is that CL is old, and Clojure is so close to be perfect if it wasn’t for Java. Clojure replaces Java, not CL and this is its strength but also its weakness.
rootnod3|16 days ago
Also, your Lisp will always behave exactly as you intended and hallucinate its way to weird destinations.
blue1|16 days ago
unknown|16 days ago
[deleted]
WolfeReader|16 days ago
lgrapenthin|16 days ago