ql-https VS cling

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...

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".

You can use SSL with QuickLisp via ql-https

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)

That what I‘m doing: https://github.com/rudolfochrist/ql-https

More recent activity, but based on clang: https://github.com/jupyter-xeus/xeus-cling https://github.com/root-project/cling

> The repl driven workflow is amazing and the lisp images are rock solid and highly performant.

do people not realize that basically everything vm/interpreted language has a repl these days?

https://www.digitalocean.com/community/tutorials/java-repl-j...

https://github.com/waf/CSharpRepl

https://pub.dev/packages/interactive

not to mention ruby, python, php, lua

hell even c++ has a janky repl https://github.com/root-project/cling

Interactive C++ with Cling, https://blog.llvm.org/posts/2020-11-30-interactive-cpp-with-cling/, https://github.com/root-project/cling/, Relaxing the One Definition Rule in Interpreted C++, https://dl.acm.org/doi/10.1145/3377555.3377901 (PDF: https://www.researchgate.net/publication/339463915_Relaxing_the_one_definition_rule_in_interpreted_C)

Want to see your mind blown? Check out cling, a (sort of) C and C++ interpreter (it's a REPL). Or the work in progress, live-developed clauf, a real C interpreter.

Cling: https://github.com/root-project/cling

Wanting to just test pure c or c++ functions that are hardware independent -> (solution that I'm using): cling just in time compiler, gives a shell that you can just experiment with C++ expressions

C++ source cannot contain a shebang, but you can make them executable with binfmt-misc, and have the kernel pass them to a C++ interpreter such as Cling upon execution. Pretty much the same as running Python or Bash scripts.