←back to thread

311 points melodyogonna | 8 comments | | HN request time: 0.434s | source | bottom
1. tree_enjoyer ◴[] No.45143384[source]
I know it's a bit of trope to say this on HN... but why not Lisp?

If I make the assumption that future ML code will be written by ML algorithms (or at least 'transpiled' from natural language), and Lisp S-Expressions are basically the AST, it would make sense that it would be the most natural language for a machine to write in. As a side benefit, it's already the standard to have a very feature complete REPL, so as a replacement for Python it seems it would fit well

replies(4): >>45143569 #>>45146098 #>>45146924 #>>45200305 #
2. layer8 ◴[] No.45143569[source]
LLMs have trouble counting parentheses accurately. ;)
replies(1): >>45144742 #
3. trallnag ◴[] No.45144742[source]
We need a lisp that is written in JSON. That should fix it
replies(2): >>45144818 #>>45147272 #
4. cjohnson318 ◴[] No.45144818{3}[source]
It would REBOLutionize everything.
5. nextos ◴[] No.45146098[source]
Yann LeCun and others created https://lush.sourceforge.net, which was a Lisp for ML.

It was probably the best option during the 2000s, and only superseded when Theano (Python) and Torch (Lua) emerged.

A Lisp comeback in this niche would be great. Python has fantastic libraries, but the language leaves a lot to be desired.

6. pjmlp ◴[] No.45146924[source]
Because it got burned in the last AI hype cycle, and many devs still think Emacs + SBCL is the only way, never even bothered to open the websites of LispWorks, Allegro Common Lisp or Clozure (not the JVM one).
7. sorry_i_lisp ◴[] No.45147272{3}[source]
https://github.com/delaneyj/jackalope
8. mlajtos ◴[] No.45200305[source]
First version of Torch was in LISP. Python is where people are, and in turn a data for LLMs.

Optimal ML lang is half-way from LISP to APL.