Common Lisp Implementations in 2023

Re:Common Lisp Implementations in 2023 by vindarel on Thursday February 23, 2023 @08:58AM (#34910635)

I quite agree, so I'm making a meta-library to have useful libraries available out of the box: https://github.com/ciel-lang/CIEL/ It's CL, batteries included. You can use it as a library, as a core CL image (loads up faster), and as a binary to have a REPL, and to run scripts:

    ciel --script myscript.lisp

where you have access to HTTP clients, JSON parsers, CSV readers, DB drivers… and much more, out of the box.

It is not done, I am dogfooding it.

[ Parent | on HN ]

Re:Common Lisp Implementations in 2023 by cellularmitosis on Thursday February 23, 2023 @09:51AM (#34911288)

I’ve noticed many lisps and schemes are not set up to simply accept a single file name as the sole command line argument, which is something common to nearly every other platform. Seems like an easy target for reducing friction for newcomers.

[ Parent | on HN ]

Re:Common Lisp Implementations in 2023 by vindarel on Thursday February 23, 2023 @10:14AM (#34911591)

Thanks for the feedback. I'll look into it, it's early enough to change.

(edit) forgot to mention we can simply call ./myscript with the right shebang line. Gets as succinct as one can.

[ Parent | on HN ]

Re:Common Lisp Implementations in 2023 by ducktective on Thursday February 23, 2023 @10:29AM (#34911800)

Excellent. It's kinda like Janet, right (in terms of being a battery-included LISP)?

[ Parent | on HN ]

Re:Common Lisp Implementations in 2023 by vindarel on Thursday February 23, 2023 @10:31AM (#34911836)

Yes, and kinda like Babashka for Clojure, in terms of fast starting scripting environment with one binary and useful built-in utilities.

[ Parent | on HN ]

Re:Common Lisp Implementations in 2023 by ducktective on Thursday February 23, 2023 @10:50AM (#34912070)

You are very active in CL community, vindarel. Thanks!

[ Parent | on HN ]