I'm happy to see ECL's restarted development! How many changes are between ECL and MKCL (MKCL was/is an ECL fork)?<p>If I'm not mistaken, ECL is (one of a few) embeddable languages that can generate a C code and provide real threads, even if used as a library.<p>[1] <a href="https://gitlab.common-lisp.net/mkcl/mkcl" rel="nofollow noreferrer">https://gitlab.common-lisp.net/mkcl/mkcl</a>
I like ECL for its ability to compile Lisp to C and have a native executable. One dream I have is to write a game using the CL-SDL2 bindings and cross compile it for Wasm; It seems possible to do now but the flow isn't very well defined. I got pretty close hacking around a month or two ago but didn't quite finish.
How does it compare to Janet <a href="https://janet-lang.org/" rel="nofollow noreferrer">https://janet-lang.org/</a> ?<p><a href="https://news.ycombinator.com/item?id=23164614">https://news.ycombinator.com/item?id=23164614</a>
<a href="https://news.ycombinator.com/item?id=28255116">https://news.ycombinator.com/item?id=28255116</a>
I am just installing from source on the tiny Linux laptop I travel with. Until recently I always paid for a LispWorks Pro license, but after retiring check out dropped that and am just using SBCL. I like the idea of having a "second Common Lisp" so I want to try out a Emacs+Slime workflow.
It would be interesting to see if writing "shell scripts" in ECL and compiling to small static binaries would work in terms of startup and execution speed.
Tangential: I wanted to embed a sane sandboxed scripting language in a node app and found… nothing. Only options were a completely broken node sub vm, half-broken js sandbox which isn’t maintained and slightly less half broken js sandbox?<p>Does everyone roll their own when they need to embed logic expressions in their yamls?