Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I find the choice of name interesting since none of the contributors seem to be Danish. Well, they could of course be Danish and have English names (like me), but I don't think so ;-)
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.
lokke seems to use Guile's tooling (compiler tower, to be specific) to compile clojure-esque code to objects understood by said Guile's tooling. This is a little different from Clojurescript's approach which use ClojureJVM to transpile to javascript. There was actually another Clojure to Scheme project that leverages Clojurescript JVM transpiler: https://github.com/takeoutweight/clojure-scheme - It targets Gambit scheme instead of Guile