serapeum VS ocicl

> both are dynamic languages with types added later in?

Common Lisp has always had types and type declarations (e.g. `the` in the hyperspec[1]) as it's part of the specification. It was not added later as far as I know.

However, `declaim` and `declare` were left very underspecified so they tend to be very implementation-specific, though there are libraries that make types more portable[2][3].

[1] http://www.lispworks.com/documentation/HyperSpec/Body/s_the....

[2] https://github.com/lisp-maintainers/defstar

[3] https://github.com/ruricolist/serapeum/blob/master/REFERENCE...

From python in lisp I want the convenience for quick scripting, which lisp doesn't have by default but of course it can be added. For example for let's you easily iterate over lines of a file or files in a directory, or anything else you add. serapeum add's convenient syntax for hashmaps (dict and @), and threading macro and plenty of utility functions, defclass-std does the boilerplate of :initarg and :accessor for you for the common cases of class declarations.

+1 for Serapeum: https://github.com/ruricolist/serapeum/blob/master/REFERENCE.md

Serapeum is an excellent CL library, with lots of utilities. You should check it out. It provides a case-like macro, to use on enums, that warns you at compile-time if you handle all the states of that enum.

Since Alexandria was mentioned may I mention Serapeum as well. Don't know if it's needed for AoC but it may be worth a look. Serapeum seems to get not enough mentions/ attention IMO.

Re: libraries; I'd like to mention serapeum which contains a ton of general purpose utilities.

I consider Serapeum to be a revamp of the Common Lisp standard: https://github.com/ruricolist/serapeum/blob/master/REFERENCE.... This provides a bunch of new features and idioms including ideas borrowed from newer languages like Clojure.

Great example of "growing a language" as a long-term evolutionary process that doesn't require changing earlier specifications in incompatible ways.

Check out ocicl as an alternative to quicklisp if you are concerned about security. Code is distributed using the OCI ecosystem (https by default, proxies work, sigstore integration, etc). https://github.com/ocicl/ocicl

If you are willing to try switching from quicklisp to ocicl, then you'll find that ocicl *does* work with authenticating proxies on Windows. https://github.com/ocicl/ocicl

> ... but still only supports one niche operating system.

1. Linux is not a niche in the target market for this project.

2. The project is written in Common Lisp with hard dependencies on SBCL-provided libraries[1], so there's reason to suspect it should work on other OSes supported by SBCL.

3. Sure, the presence of Makefile and sb-posix imply it requires a POSIX compliant OS, but Linux is not the only one that fits the bill.

4. The included Linux-only binary 'oras' is clearly a vendored artifact, not part of this project, and clearly an OCI client. A simple search shows it is indeed cross-platform[2].

Perhaps you should try what almost every Linux user has had to do when encountering software actually built for only one "niche" operating system that they want to use on their OS: look.

1. https://github.com/ocicl/ocicl/blob/170aff0/ocicl.asd#L34

2. https://github.com/oras-project/oras/releases