awesome to see SBCL so active.<p>newcomers to Lisp, check out:<p>- <a href="https://github.com/CodyReichert/awesome-cl" rel="nofollow">https://github.com/CodyReichert/awesome-cl</a> (there might be more libraries than you think)<p>- <a href="https://lispcookbook.github.io/cl-cookbook/" rel="nofollow">https://lispcookbook.github.io/cl-cookbook/</a><p>- how to create a project (with my project generator): <a href="https://www.youtube.com/watch?v=XFc513MJjos" rel="nofollow">https://www.youtube.com/watch?v=XFc513MJjos</a>
I love lispy languages— Clojure being the one I’m most familiar with, but it’s hard to give up static types.<p>Anyone here worked on a large lisp codebase? How big was it? How big was the team? What’s the secret sauce?
The opposite —- calling python libraries directly from Lisp, like you can from Julia — would be much more useful. No adult wants to use python, but for some reason it is replete with yummy libraries.
Interesting, one of the reasons I use Scheme over Common Lisp is that doing this in CL is not common or easy.<p>Scheme has few options to generate C code and it's so simple that I can write my own transpiler in no time.
External callable is good and is that easy.<p>But is lisp good for library construction and for other system to use. Many languages are not in this niche (is swift or apple os easily callable if not using objective c), but Common Lisp gives an impression it is more like it to be the centre, if not hotel California like. In fact one key feature or bug is it’s dynamic nature - debugging, typing, object and method etc - might be lost. In this regards callable from outside and unlike c which is not built for others (as os is to be called) one wonder what is to be gained.<p>Obviously it could be one of the foundation of a large system. But can the satellite be others is my question. Can I have CL core and say python front end etc.