ql-https
npt
Our great sponsors
ql-https | npt | |
---|---|---|
6 | 5 | |
16 | 161 | |
- | - | |
7.7 | 0.0 | |
about 2 months ago | about 1 year ago | |
Common Lisp | C | |
MIT License | The Unlicense |
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.
ql-https
-
It's 2023, so of course I'm learning Common Lisp
Solutions for the lack of https:
- add in https://github.com/rudolfochrist/ql-https (downloads packages with curl)
- use another package manager, CLPM: https://www.clpm.dev (or the newest ocicl)
> CLPM comes as a pre-built binary, supports HTTPS by default, supports installing multiple package versions, supports versioned systems, and more.
- use mitmproxy: https://hiphish.github.io/blog/2022/03/19/securing-quicklisp...
-
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".
-
What do you think the risks/pitfalls of using Common Lisp are in a business?
You can use SSL with QuickLisp via ql-https
- quicklisp security (or total lack of it)
-
Common Lisp Implementations in 2023
LPM's warning is not surprising. It's common for libraries (dare I say open-source ones?), even if they work well. It's part of the stability game, once they are marked 1.0, they are stable. LPM works well (as reported by others).
QL wants to do it portably, there are easy workarounds, but yeah…
(just saw https://github.com/rudolfochrist/ql-https)
-
Securing Quicklisp through mitmproxy
That what I‘m doing: https://github.com/rudolfochrist/ql-https
npt
-
Common Lisp Implementations in 2023
No love for NPT (<https://github.com/nptcl/npt>)? Well, I get it, it is very, very new.
One note about ABCL is that it doesn't support TCO, which the Common Lisp spec doesn't mandate. For people who want a Lisp on the JVM and really want tail calls, I would recommend checking out Kawa (<https://www.gnu.org/software/kawa/index.html>).
-
Common Lisp running natively over WebAssembly for the first time ever
based on the conversation on IRC it is npt: https://github.com/nptcl/npt
- npt - an implementation of ANSI Common Lisp in C
- Npt – an implementation of ANSI Common Lisp written in C
What are some alternatives?
CSharpRepl - A command line C# REPL with syntax highlighting – explore the language, libraries and nuget packages interactively.
quicklisp-client - Quicklisp client.
tungsten - A Common Lisp toolkit.
bettercap - The Swiss Army knife for 802.11, BLE, IPv4 and IPv6 networks reconnaissance and MITM attacks.
alive - Common Lisp Extension for VSCode
thirteen-letters - Competitive word scramble in the browser, made for Lisp Game Jam (Spring 2023)
quicklisp-https
qlot - A project-local library installer for Common Lisp
BDFProxy - Patch Binaries via MITM: BackdoorFactory + mitmProxy.
ultralisp - The software behind a Ultralisp.org Common Lisp repository
LASS - Lisp Augmented Style Sheets
mitm6 - pwning IPv4 via IPv6