hissp VS awesome-cl

Hissp is a Python library that can compile a whole program into one Python expression.

If you want Python to be as customizable as Lissp, check out Hissp (and Hebigo).

Hissp is really cool for metaprogramming Python. There's also macropy, but it's harder to use.

I prefer https://github.com/gilch/hissp, where Hy has to use shims to pretend statements are expressions, Hissp just targets the expression subset in the first place. (though as you mentioned, hy has a lot of literature and support around it, where as you're going to have to find your own way around hissp)

No shortage of options, e.g. Dg, Mochi, Coconut, and Hebigo (based on Hissp[1]).

[1]: https://github.com/gilch/hissp

If you want Lisp metaprogramming plus Python ecosystem, check out Hissp

Hissp is really interesting. Read through the docs and you'll understand Python more deeply. It works well with Toolz and Pyrsistent.

I like History but I'll comment about Lisp in web apps today, if I may. We have a choice of web servers and web libraries (https://github.com/CodyReichert/awesome-cl/#web-development), and we live in happy times where HTMX or Datastar are great fit for Lisp -as with any stack. See these Datastar examples built in CL: https://github.com/fsmunoz/datastar-cl I use and like the Mito ORM too, which comes with automatic migrations and, since last year, a composable query engine (SxQL).

Here you will find some screenshots of some of today's web applications built in CL: http://lisp-screenshots.org/ and here an opinionated tutorial: https://web-apps-in-lisp.github.io/ One example: ScreenShotBot https://screenshotbot.io/ a successful open-source product and company. It now replaced Facebook's automatic screenshot testing tool (source: their blog).

The incremental development and interactive top-level are still precious and unmatched.

Pretty good, except and I don't share the advice to use package-inferred-systems, like, at all. It hides the third-party libraries you rely on, it prevents you from using one package in multiple files (a flexibility not common out there), you can't see the project's structure at first glance… just use a simple .asd file declaration, you'll be fine.

more: https://lispcookbook.github.io/cl-cookbook/

libraries: https://github.com/CodyReichert/awesome-cl/

I'll invite to explore the CL ecosystem starting with https://github.com/CodyReichert/awesome-cl/ (it might be larger than one thinks)

In terms of asynchronous programming, not built-in to implementations (like, no green threads), we have

- https://github.com/orthecreedence/wookie - an asynchronous HTTP server

- https://github.com/fukamachi/woo - fast non-blocking HTTP server on top of libev.

- an actor-based task manager for Hunchentoot: https://github.com/mdbergmann/cl-tbnl-gserver-tmgr

see also https://github.com/CodyReichert/awesome-cl/#parallelism-and-... for promise libraries, async libraries, the actor library, an STM library, lparallel (run tasks in parallel, easy and often useful), bindings to other async tools.

Those libraries are active.

for folks looking for libraries: https://github.com/CodyReichert/awesome-cl/

(I don't know for popularity but my personal opinion is that CL is still unmatched: this level of interactive development + good debugging tools + excellent implementation that compiles to fast machine code + fast startup for binaries + self-contained binaries + stable yet improving language, implementations and ecosystem + connect from a running program + commercial vendors if you need + … such a unique and productive set)

But where is it now? If not mainstream, where? Is it not used at all, or only by hobbyists, or also by successful companies, today? If it isn't mainstream, is it important, if not, what's the cursor?

elements to not judge in the void https://github.com/azzamsa/awesome-lisp-companies/ (some are hiring) (that's just the companies we know, nothing official)

https://github.com/CodyReichert/awesome-cl/

https://github.com/CodyReichert/awesome-cl#library-manager

I think https://github.com/CodyReichert/awesome-cl with a bit more trimming/tagging and interactivity (e.g. show all "stars") to empower users to explore the ecosystem and build their own image is a better way.

There should also be a large disclaimer saying "Consider disregarding portability in favour of SBCL to get a more modern experience".

awesome-cl

It looks like CL is all the rage for quantum computing (and some AI companies).

https://github.com/CodyReichert/awesome-cl

Thinking about recent feedback:

- https://blog.funcall.org//lisp%20psychoacoustics/2024/05/01/... (https://news.ycombinator.com/item?id=40233736) (2024)