The tools for common lisp make it very hard to get converts

• common-lisp-jupyter

  3 202 6.3 Common Lisp

  A Common Lisp kernel for Jupyter along with a library for building Jupyter kernels.

Thanks for pointing to this. Now I gotta give common-lisp-jupyter a try

• portacle

  37 678 3.6 Shell

  A portable common lisp development environment

  

Indeed, I'm not convinced that Emacs is so uniquely onerous, or that it puts Common Lisp into a particularly bad position. With lisp-in-a-box IDEs like [Portacle](https://portacle.github.io/), the friction to start coding Common Lisp in Emacs is pretty darn low: I had an easier time getting started with Common Lisp in Portacle than Python in PyCharm, and I certainly wouldn't say PyCharm is tough to use! Portacle doesn't require you to interface with a whole lotta Emacs, and CUA keybindings are just a menu option away if you need them. "Download and extract a single program for a fully-featured Common Lisp solution" is about as approachable as it gets.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• cormanlisp

  5 568 10.0 Common Lisp

  Corman Lisp

  

After making this post, I came across another Common Lisp distribution called CORMAN LISP . It is a Windows-only CL distribution that comes prepackaged with a CL wrapper for the Win32 API, meaning you can write GUIs directly in CL. It also comes with its own IDE that is not Emacs.

Suggest a related project