New Lisp-Stat Release

Post by medo-bear » Thu, Jul 21, 2022, 7:00 PM UTC

piethesailorman wrote: post #41

p1esk wrote: post #38

Earlier quoted context omitted.

There's not even a convolutional layer provided as a building block. This project looks pretty dead to me: most of the code is 8 years old, and the last code-changing commit is over 2 years old. I guess it's okay as a proof of concept for ML with Lisp, but I don't think anyone interested in ML would actually consider using it.

In defense of common lisp: The language is ansi standard and hasn't seen core changes in decades. This means cl pagckages can be "done". It is very common in cl to have projects that haven't been touched in years, because it is highly unlikely to break, hence, "it just works". As for this specific ML conversation, I am not in this field and have nothing valuble to say about who uses what and how viable/appropriate an…

Post by piethesailorman » Thu, Jul 21, 2022, 7:48 PM UTC

medo-bear wrote: post #42

piethesailorman wrote: post #41

Earlier quoted context omitted.

In defense of common lisp: The language is ansi standard and hasn't seen core changes in decades. This means cl pagckages can be "done". It is very common in cl to have projects that haven't been touched in years, because it is highly unlikely to break, hence, "it just works". As for this specific ML conversation, I am not in this field and have nothing valuble to say about who uses what and how viable/appropriate an…

> his means cl pagckages can be "done". this is true if there is nothing functional that can be added to a package. however its very much not true for ml frameworks right now. new things are being added all the time in the field. however even in the package i linked you have the necessary ingredients for any deep learning model: cuda and back propagation. the other person mentioned convolution which i think is pretty…

Post by vindarel » Thu, Jul 21, 2022, 8:52 PM UTC

mrbukkake wrote: post #43

(ql:quickload :plot/vega) isn't working for me with the latest quicklisp dist, what am I doing wrong

Post by Lisp-Stat » Thu, Jul 21, 2022, 11:09 PM UTC

bobochan wrote: post #47

vindarel wrote: post #46

Earlier quoted context omitted.

Quicklisp ships releases once a month (think Debian releases instead of npm), so it is very possible it didn't pick the latest release yet. Your solution is to clone the repository into ~/quicklisp/local-projects/. Another one would be to use the Ultralisp distribution, that ships every five minutes. https://ultralisp.org/ (ql-dist:install-dist " http://dist.ultralisp.org/ " :prompt nil) and now you could quickload p…

I gave this a try but still ran into issues. First it was a missing file, description.text, so I created a temporary one, but have not been able to figure it out after going through all of the different possibilities on the web site and github. I am going to keep an eye on this project because I would really like to be able to work on this. Hopefully updates in a month or so will get things in sync.

Post by bobochan » Thu, Jul 21, 2022, 11:50 PM UTC

Lisp-Stat wrote: post #48

bobochan wrote: post #47

Earlier quoted context omitted.

I gave this a try but still ran into issues. First it was a missing file, description.text, so I created a temporary one, but have not been able to figure it out after going through all of the different possibilities on the web site and github. I am going to keep an eye on this project because I would really like to be able to work on this. Hopefully updates in a month or so will get things in sync.

FIXED. That's a new file to help with the auto generated API documentation and it's possible one was missed at checkin. Vindarel has correctly identified the main problem though, Quicklisp hasn't yet picked up the new files.