4 ms·
For my comparative programming class in college, I was the only person who got all the Lisp assignments done on time and correctly (it helped that I was deeply
by WillAdams 3y ago
For my comparative programming class in college, I was the only person who got all the Lisp assignments done on time and correctly (it helped that I was deeply into TeX at the time), so there is definitely a mind-frame to be in, and some sort of hurdle which a fair percentage of folks find difficult.
One big problem w/ Lisp is that it is so difficult to distribute programs written using it --- I'd give a lot for the ability to compile to a stand-alone program which could then be distributed.
- massysett 3y agoSBCL has save-lisp-and-die. The binaries are big though. LispWorks will give you smaller binaries, but it costs money.
- mark_l_watson 3y agoWhen you build SBCL from source, enable the compressed heaps option. Then when you create an app with save-lisp-and-die, you get a fairly small app even without having a treeshaker to remove unused code.
- vindarel 3y agoMy web app with dozens of dependencies is ±35MB, using SBCL core compression. So that's heavier than Rust, lighter than Deno, maybe in par with Go when the application grows. It starts up in 0.4s, without compression it does in 0.01s. https://lispcookbook.github.io/cl-cookbook/scripting.html#building-a-smaller-binary-with-sbcls-core-compression https://lispcookbook.github.io/cl-cookbook/scripting.html#bu...