←back to thread

Hofstadter on Lisp (1983)

(gist.github.com)
372 points Eric_WVGG | 1 comments | | HN request time: 0s | source
Show context
dahart ◴[] No.41860159[source]
> Why is most AI work done in Lisp?

That’s changed, of course, but it remained true for at least another 15 or 20 years after this article was written and then changed rather quickly, perhaps cemented with deep neural networks and GPUs.

Other than running the emacs ecosystem, what else is Lisp being used for commonly these days?

replies(14): >>41860189 #>>41860283 #>>41860409 #>>41860450 #>>41860590 #>>41860851 #>>41861146 #>>41861256 #>>41861289 #>>41861317 #>>41861331 #>>41861541 #>>41861549 #>>41866917 #
nextos ◴[] No.41860851[source]
> Why is most AI work done in Lisp?

Yann LeCun developed Lush, which is a Lisp for neural networks, during the early days of deep architectures. See https://yann.lecun.com/ex/downloads/index.html and https://lush.sourceforge.net. Things moved to Python after a brief period when Lua was also a serious contender. LeCun is not pleased with Python. I can't find his comments now, but he thinks Python is not an ideal solution. Hard to argue with that, as its mostly a thin wrapper over C/C++/FORTRAN that poses an obvious two-language problem.

replies(3): >>41861189 #>>41861684 #>>41862306 #
1. sourcepluck ◴[] No.41861189[source]
Hadn't seen that before, very interesting!