Modern, functional Common Lisp: myths and best practices

> Building common lisp is a pain, because packaging/ASDF is terrible and you don't easily get a nice and small statically linked executable out either.

https://www.xach.com/lisp/buildapp/

http://www.sbcl.org/manual/#index-save_002dlisp_002dand_002d...

https://ccl.clozure.com/manual/chapter4.9.html

[ Parent | on HN ]

Re:Modern, functional Common Lisp: myths and best practices by patrec on Wednesday February 26, 2020 @09:40AM (#22423267)

If you think spamming random links to old toy/dead/in-house projects you found on Cliki and that contained words like "machine learning", "Games" or "GUI" (mcclim – really?[]) constructs an effective rebuttal to "no ecosystem to speak of", I'm not sure I know what to say. But I'll go through your list in more detail if you want me to.

[] For the record CLIM had interesting ideas, but last I looked, calling McCLIM's implementation of them a toy would be charitable.

[ Parent | on HN ]

Re:Modern, functional Common Lisp: myths and best practices by yellowapple on Wednesday February 26, 2020 @04:06PM (#22427326)

The claim was "no eco-system to speak of". There is clearly an ecosystem to speak of. It might not be a healthy ecosystem, and we might speak of it poorly, but it exists nonetheless, and in fact exists in a greater capacity across that whole range of categories than what a lot of other "popular" languages can claim.

"Machine learning" is a perfect example of how out-of-touch that claim is considering that Lisp was the language for AI research until very very recently.

> mcclim – really?

I guess you didn't see the link right below it with the dozens of other bindings to other popular GUI toolkits.

[ Parent | on HN ]