quicklisp-projects VS janet

Where is it getting that system name from though? I thought quicklisp used project dir names: https://github.com/quicklisp/quicklisp-projects/blob/8aa3500e9c3c3c7e03e76675410008b7e4c4c42f/projects/jzon/source.txt

The tracking issue for adding cl-djula-svg to quicklisp is here. You may want to check it for any updates.

Why do you need to build them in when you can just load your favorite libraries that do these functions with https://www.quicklisp.org/ , especially for http the great libraries by Fukamachi: https://github.com/fukamachi parallel processing: https://lparallel.org/ etc.

I'm very grateful that common lisp does not version up (like python), but you can always load a new or newer version of libraries with no impact on your core production code. (Such as a rewrite when the language gets a new version - this never happens with Common Lisp)

QUICKLISP comes with a regularly updated software distribution, see quicklisp-projects. This software distribution is pulled once when QUICKLISP is installed and can be later updated with (ql:update-all-dists). Once a project is added to the QUICKLISP dist, its updates are also added regularly and are available to users who care of issuing (ql:update-all-dists).

Testing on quicklisp-projects

The Common Lisp bindings to GTK can be installed with Quicklisp. If you don't already have Quicklisp installed, it's painless. See the Quicklisp website for more details, but here's an example of installing Quicklisp on Debian and configuring SBCL. The steps should be the same for any Linux distro and macOS.

I've noticed that beta.quicklisp.org no longer resolves. Neither does https://www.quicklisp.org/. What's going on?

As for the packages themselves, you can look at the repository information for each package at https://github.com/quicklisp/quicklisp-projects and use that to get the packages yourself manually. Most of them just use the latest commit in the package's respective git repos. A few use specific tags. Some, have to be gotten by other means. It is always possible, by looking at the quicklisp update data listing all the packages, to get the url for the package tarballs on the quicklisp server and download them manually.

Seems like a perfect use-case for Janet. (https://janet-lang.org/) A fast minimal VM like Lua, but even more extensible than Lua by being a "Lisp" with macro and C extension capabilities. Not a true Lisp, it's very pragmatic and performance-oriented. But it keeps the good stuff.

You might be looking for: https://janet-lang.org/

It comes with a build tool `jpm` which installs dependencies globally by default, but you can have it be installed in your project folder as well.

I like Clojure, but I never had any good opportunities to use it other than for a few small hobby projects. It is unfortunate that it is so huge with tons of dependencies and no simpler native implementation. I started looking at various LISPs and Schemes to find something lighter to use instead and ended up settling for Janet that I think is Clojure-like enough to be comfortable to use, but in a small native binary with no dependencies and can be embedded in other native programs. I am sure for big, real, projects that Clojure makes more sense, but for my hobby projects and scripts I do not think I will install it again. I am still happy for the things I learned from learning Clojure. It was a real eye-opener for an old OO-programmer.

https://janet-lang.org/

One might also check out Janet for quick scripting tasks.

https://janet-lang.org

Thanks!

I thought about another multiplatform, homoiconic, highly compact language: https://janet-lang.org/ (takes 803 kb on my machine).

It has no types though.

Racket is great, and if you like it you might find Rash interesting:

https://rash-lang.org/

Janet and Gerbil Scheme are also worth a look:

https://janet-lang.org/

https://cons.io/

Point here is that, for instance Janet language does not have cons / pair type but tuple (and so is lispoid, not lisp), but clearly this is sufficient for macros & hence seamless language construction: all you need is to be a lispoid although being a lisp gives another useful feature.