quicklisp-projects
Our great sponsors
| quicklisp-projects | quicklisp-https | |
|---|---|---|
| 8 | 3 | |
| 411 | 1 | |
| - | - | |
| 8.2 | 0.0 | |
| 5 months ago | almost 7 years ago | |
| Common Lisp | ||
| - | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
quicklisp-projects
-
System "jzon" not found
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
-
Using SVGs in Common Lisp web apps with Djula
The tracking issue for adding cl-djula-svg to quicklisp is here. You may want to check it for any updates.
-
Lisp in 99 lines of C and how to write one yourself [pdf]
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)
-
Common Lisp 3D graphics code repo - very preliminary
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).
-
An experiment: cl2nix to assist lispPackages (WIP)
Testing on quicklisp-projects
-
Learn Common Lisp by Example: GTK GUI with SBCL
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.
-
What happened to Quicklisp?
I've noticed that beta.quicklisp.org no longer resolves. Neither does https://www.quicklisp.org/. What's going on?
-
Why do people use Quicklisp although it is known to be vulnerable to man-in-the-middle attacks?
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.
quicklisp-https
-
Ocicl – An ASDF system distribution and management tool for Common Lisp
Other options are:
- Quicklisp -really slick, libraries in there are curated. (with https support here: https://github.com/rudolfochrist/ql-https and here: https://github.com/snmsts/quicklisp-https.git)
- for project-local dependencies like virtualenv: https://github.com/fukamachi/qlot
- a new, more traditional one: https://www.clpm.dev (CLPM comes as a pre-built binary, supports HTTPS by default, supports installing multiple package versions, supports versioned systems, and more)
For recent Quicklisp upgrades: http://ultralisp.org/
Ocicl is very new (5 days) and tries a new approach, building "on tools from the world of containers".
-
quicklisp security (or total lack of it)
I use this on a system that has curl to safely bootstrap https://github.com/snmsts/quicklisp-https.git which then uses openssl via dexador so that I can drop the curl dependency. A bit of a dance to get everything up and running, but once it is done for a given system you are good to go.
-
Why do people use Quicklisp although it is known to be vulnerable to man-in-the-middle attacks?
https://github.com/snmsts/quicklisp-https/blob/master/quicklisp-https.asd#L7 ?
What are some alternatives?
kons-9 - Common Lisp 3D Graphics Project
BDFProxy - Patch Binaries via MITM: BackdoorFactory + mitmProxy.
ulisp-zero - A pared-down version of uLisp for hackers.
quicklisp-client - Quicklisp client.
caveman - Lightweight web application framework for Common Lisp.
ql-https - HTTPS support for Quicklisp via curl
aserve - AllegroServe, a web server written in Common Lisp
oras - OCI registry client - managing content like artifacts, images, packages
BuildYourOwnLisp - Learn C and build your own programming language in under 1000 lines of code!
qlot - A project-local library installer for Common Lisp
djula - Common Lisp port of the Django templating language
ocicl - An OCI-based ASDF system distribution and management tool for Common Lisp