pod-registry VS roswell

babashka supports html parsing through pods:

https://github.com/babashka/pod-registry

Pods can be written in any language and they can expose functions to babashka by implementing a protocol.

One pod exposing HTML parsing is:

https://github.com/retrogradeorbit/bootleg

Here is an example of how to use that:

https://github.com/babashka/pod-registry/blob/master/example...

This is not how babashka (or the underlying sci interpreter) works: babashka doesn't transpile to another language, but directly executes the code (via an intermediate analyzed representation). Babashka (and sci) are implemented on the JVM in Clojure itself and can leverage libraries directly from that ecosystem, without re-implementing everything for a different host than the JVM. A bb (or sci) program consists of pre-compiled Clojure code (via GraalVM native-image) and interpreted glue code. It aims to be as compatible as possible with JVM Clojure. Babashka integrates with tools.deps.alpha and can execute several existing Clojure libraries "as is" (https://github.com/borkdude/babashka/blob/master/doc/projects.md). It aims to be as compatible as possible with JVM Clojure. With the introduction of pods (https://github.com/babashka/pod-registry) it is able to leverage libraries from other ecosystems as well.

BTW, Roswell makes it easier to run scripts: https://github.com/roswell/roswell/wiki/Roswell-as-a-Scripti...

It is also a tool to install various CL implementations, and to install software.

It doesn't come with a choice of built-in libraries.

The Github wiki: https://github.com/roswell/roswell/wiki

download failed "https://github.com/roswell/roswell/releases/download/21.10.14.111/roswell_21.10.14.111_amd64.zip" 404 "Not Found"

You could also be a roswell user, in which case your project might have a roswell directory. Again, you can look at the qlot project for reference.

Clack is a web application environment for Common Lisp inspired by Python's WSGI and Ruby's Rack. Clack provides a script to start a web server. It's useful when you deploy to production environment. You need to install Roswell before as Clack depends on it.

Common Lisp itself has Roswell, which I am disappointed to see is not even mentioned in the article.

https://github.com/roswell/roswell

w.r.t to image size, ScriptL takes care of that since everything is in the same image. You could also use something like buildapp or cl-launch to make a multi-call binary that you compile your scripts into. I think I recall roswell allowing multiple entry points too, but I never could get it to work. Possibly PEBKAC on my end.