logoalt Hacker News

stackghostyesterday at 8:59 PM1 replyview on HN

I use emacs regularly (in fact I have it running right now) and I think the complaints against it are perfectly valid. Emacs is awesome in lots of ways, but it also really, really sucks in lots of other ways.

But putting emacs aside, the SBCL tooling seems reasonable to me. The real reason I rarely reach for lisp these days is not the tooling, but because the Common Lisp library ecosystem is a wasteland of partial implementations and abandoned code bases.

It's also been my experience that LLMs are better at writing more mainstream languages, especially "newbie-proof" languages like Go.

In any case, I don't see why one would reach for Allegro or Lispworks over SBCL unless one really enjoys writing lisp by hand and needs specific features they offer that SBCL doesn't. I would imagine those features are vanishingly few.


Replies

vindarelyesterday at 11:03 PM

I'd prefer that a LispWorks user answer, but there are quite a few interesting features, such as:

- tree shaking and small binaries (±5MB a GUI app)

- the CAPI cross-platform and native GUI toolkit

- mobile platforme runtime (iOs, Android)

- its Java interface

- its KnowledgeWorks system for "rule-based, object-oriented, logical, functional and database programming"

- more?

ps: today we maintain a list of pretty decent libraries: https://github.com/CodyReichert/awesome-cl/