portacle VS sbcl

Thanks for your work! I can definitely see how your project improve CL's accessibility. Not sure if you're aware of the Portacle project, but I think there is an opportunity merging two projects together.

Also it is not much of a kit either since the user is left to install all the tools on their own. User who wants an easy to start kit with Emacs baked in is much better using Portacle or clean Emacs, or some of more polished Emacs distributions like Doom or Prelude together with Roswell for the "kit" part.

Then there's Portacle, a portable Emacs with SBCL, Quicklisp and Emacs goodies (magit, file-tree…) pre-installed. https://portacle.github.io/

See also Portacle: https://portacle.github.io/ It is a portable Emacs that is ready-to-use for CL: it comes with Slime, some Emacs packages, Quicklisp and git.

Others have covered the language, but you'll also want tooling. An easy one to get started with is Portacle. It's a Lisp compiler, emacs with Lisp plugins, QuickLisp package manager, etc. so you don't have to spend time setting it all up.

1) I also love VSCode ... but for Lisp Emacs really is so much better. Look at Portacle. It basically is Emacs that's well configured for Common Lisp with SBCL right out of the box. You'll have to learn how SLIME work (the shortcuts to recompile running Lisp, etc).

Lisp (Common Lisp: https://portacle.github.io/ and my fav Lisp dialect: janet-lang.org),

Have a look at Portacle, which is meant to be more or less what you're looking for: an out-of-the-box functional CL IDE.

download Allegro CL free edition https://franz.com/downloads/clp/survey or Lispworks personal edition http://www.lispworks.com/downloads/index.html to get started. There is also a bundled Emacs+SBCL called Portacle https://portacle.github.io/ but with this you are simultaneously learning Emacs and CL that may be overwhelming even for seasoned programmers.

Based on the commit message [0], and the references to "user code" in this document, my guess is that user programs have or will have access, but it's not finalized enough to be documented.

That being said, I suppose if you're developing an internal API for a compiler/interpreter, your "users" could be other parts of the project rather than language users.

https://github.com/sbcl/sbcl/commit/7f65522a16d857e41aa61cd0...

related: the Immix inspired parallel-mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently into SBCL.

https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...

https://applied-langua.ge/~hayley/swcl-gc.pdf

build with

    ./make.sh --without-gencgc --with-mark-region-gc (on x86-64/Linux and x86-64/macOS only at the moment).

The Immix inspired mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently, which is pretty cool news for SBCL users.

>Just like your usual hardware CPU cannot run Common Lisp directly, neither can WASM.

My usual hardware CPU runs Common Lisp code beautifully, thanks to this native x86-64 compiler: https://www.sbcl.org/

You can get SBCL for free which actually beats Lispworks on performance AFAIK: https://www.sbcl.org/

sbcl w/ linedit for repl/shell