Re:A Retrospective on Paradigms of AI Programming (2002)
by varjag on Monday March 27, 2023 @04:18AM
(#35324187)
Common Lisp has certainly better array and vector support than Python so this can't be it.
Re:A Retrospective on Paradigms of AI Programming (2002)
by gcr on Monday March 27, 2023 @08:12AM
(#35325648)
on the minimal chance you're not being sarcastic, could you say more about this?
Re:A Retrospective on Paradigms of AI Programming (2002)
by varjag on Monday March 27, 2023 @10:12AM
(#35326891)
Common Lisp has has native support for vectors and arrays. They can be adjustable or fixed size, displaced to other arrays (kind of a "view" with a different geometry), specialized on elements of particular type or generic. For adjustable vectors you can specify their allocation growth increments for push operations. Or pre-allocate adjustable arrays but specify a lower initial size. Arrays can be accessed in row-major order mapping them into vectors etc etc.
Foreign function interface of different implementations typically provide a way to access C allocated memory areas as Lisp arrays.
Re:A Retrospective on Paradigms of AI Programming (2002)
by mistrial9 on Monday March 27, 2023 @11:28AM
(#35327967)
numpy changed the ecosystem dramatically.. the combination of engineering-efficient matrix math, plus the plug-and-play, low barriers to entry broad ecosystem, tipped the scales and it never went back. Millions of coders literally are playing and implementing using these python stack tools.
Re:A Retrospective on Paradigms of AI Programming (2002)
by varjag on Monday March 27, 2023 @03:10PM
(#35330965)
The efficient part in numpy is certainly not the Python code.
Re:A Retrospective on Paradigms of AI Programming (2002)
by vkazanov on Monday March 27, 2023 @05:00PM
(#35332520)
Yes but what difference does it make? The interface is python.
Besides, libraries are much less rigid than language features so maintainers can and do iterate on these much faster.
Saying this as a big Lisp/scheme/emacs fan, btw.
Re:A Retrospective on Paradigms of AI Programming (2002)
by varjag on Tuesday March 28, 2023 @05:27AM
(#35337909)
What I was getting at is the reason why Python is popular and CL isn't is not technical but social.
Re:A Retrospective on Paradigms of AI Programming (2002)
by pharmakom on Monday March 27, 2023 @04:58PM
(#35332498)
But this is fundamentally a native code library and we can bind it to any language that supports this. Nothing unique to Python here.
Re:A Retrospective on Paradigms of AI Programming (2002)
by mistrial9 on Monday March 27, 2023 @05:00PM
(#35332539)
except, evolution (and market share) are built in things that really exist now. So .. millions of users, I would emphasize that part today.
Re:A Retrospective on Paradigms of AI Programming (2002)
by User23 on Monday March 27, 2023 @11:01AM
(#35327576)
Why would you think it’s sarcasm? Modern Common Lisp implementations not only generate well optimized code, they make it simple to check what’s really happening with DISASSEMBLE.
Re:A Retrospective on Paradigms of AI Programming (2002)
by gcr on Monday March 27, 2023 @06:11PM
(#35333465)
i am genuinely curious, because I think CL could do some amazing things in the symbolic algebra/compiler space here. Tensorflow's AutoGrad and AutoGraph (and I think JAX maybe) had to do terrible things to the python bytecode interpreter to compile methods, and Theano only worked by overhauling the entire number tower and adding its own control flow.
If CL could become a frontend for XLA perhaps, then maybe we can go full circle and turn Torch back into the lisp project it originally started out as!
Re:A Retrospective on Paradigms of AI Programming (2002)
by bitwize on Tuesday March 28, 2023 @05:16PM
(#35347987)
That's why the numeric kernels, where all the speed-sensitive array and vector processing is done, are written in C++ or Fortran.
Re:A Retrospective on Paradigms of AI Programming (2002)
by freilanzer on Monday March 27, 2023 @06:13AM
(#35324831)
Not really, it just lacks the ecosystem. Rapid feedback cycles, prototyping, introspection, performance, etc. would actually make it the ideal language. If CL 2.0 came out today it would be ideal for ML/DL.
Re:A Retrospective on Paradigms of AI Programming (2002)
by pharmakom on Monday March 27, 2023 @04:57PM
(#35332480)
I have vague hopes that a Clojure implementation liberated from the JVM can be this language.
Re:A Retrospective on Paradigms of AI Programming (2002)
by gcr on Monday March 27, 2023 @08:46AM
(#35325962)
Practitioners make distinctions between machine learning (statistical analysis + optimization) and artificial intelligence (symbolic reasoning) for important reasons. For starters, machine learning systems based on matrix multiplies and accumulation are fundamentally unexplainable in human terms; for others, they're applied to different problems (path planning and game-playing started as AI problems, and haven't seen statistical optimization applied until very recently)
Re:A Retrospective on Paradigms of AI Programming (2002)
by User23 on Monday March 27, 2023 @10:59AM
(#35327545)
Out of curiosity have you ever done any nontrivial development in a production quality Lisp using appropriate tooling like Emacs/SLIME or one of the proprietary IDEs? It’s exactly the programming environment that would be optimal for an interactive coding dialog with a LLM.
Re:A Retrospective on Paradigms of AI Programming (2002)
by pharmakom on Monday March 27, 2023 @04:55PM
(#35332452)
Nothing stopping a lisp language from manipulating native data structures just like we do in Python.
I think that Python is actually kinda bad as a language for writing logic and building abstractions. We’re still using it for AI because that’s a small part of building these systems and inertia trumps everything.
Lisp is, almost, the opposite of a language you would choose to do AI in today.