Re:How to Write a (Lisp) Interpreter (In Python) (2010)
by pjmlp on Tuesday March 12, 2024 @04:46AM
(#39677409)
The difference is that Lisp doesn't require a two language syndrome.
Julia, Mojo, XLA, Triton,... are picking up speed, and the pressure for a JIT on CPython is increasing from Microsoft and Facebook, exactly because not everything is AI, and not everyone wants to write C++, C to speed up Python.
Re:How to Write a (Lisp) Interpreter (In Python) (2010)
by ja321 on Tuesday March 12, 2024 @03:14PM
(#39683620)
Ok the other hand, a good lisp implementation of neural nets would offer a specific set of macros dedicated to matrix operations. This set of macros is, in the lisp point of view, a domain specific language. So, you still have 2 languages.
The compute intensive parts of AI already always happen in CUDA/C++/C.