46 ms·

I particpated in a Clojure reading group for "Getting Clojure" back around 2017. Having the entire JVM ecosystem available, is absolutely a great benefit. I eve

I particpated in a Clojure reading group for "Getting Clojure" back around 2017. Having the entire JVM ecosystem available, is absolutely a great benefit. I even fooled around with ClojureScript a bit. David Nolen is great at making the case for both.

jlarocco 2mo ago
On a related note, there's a cross-platform Common Lisp package, "Bike" https://github.com/Lovesan/bike https://github.com/Lovesan/bike, that lets you use .Net assemblies from Common Lisp. I've used it a tiny bit at work (on Windows) and at home (on Linux), and ran into one issue with "out" parameters, but otherwise it works really well.
- nobleach 2mo ago
  That's just crazy! (in a good way) I've been in software since 1998 and it's like I've just uncovered a whole new world.
  - vindarel 2mo ago
    What about this one? https://github.com/dotcl/dotcl https://github.com/dotcl/dotcl > Common Lisp implementation on .NET. Lisp source is compiled to CIL (Common Intermediate Language) and runs on the .NET JIT — so the same Lisp image runs on Windows, macOS, and Linux across x86-64 and ARM64 without per-platform porting work.
    - jlarocco 2mo ago
      Thanks! I don't think I've seen that one.
arikrahman 2mo ago
Now there's Jank too, the first time a Lisp dialect has reached into native world since Clasp. The way it interops Clojure with the LLVM is unprecedented.
- Jtsummers 2mo ago
  > the first time a Lisp dialect has reached into native world since Clasp. What's that supposed to mean? Many (probably most if we only consider the non-toy ones) lisp implementations are "native" (compiling to native machine code, not interpreted).
  - erichocean 2mo ago
    You can directly call C++ as C++, not via a C ABI.
    - Jtsummers 2mo ago
      > You can directly call C++ as C++, not via a C ABI. That's a unique definition of "native". It suggests that C is not a native language, which is going to be a hard thing to convince others of.
      - didibus 2mo ago
        Ya, I think that was a bit misspoken. They mostly meant direct C and C++ interop. It feels much less like a traditional FFI and more like using C and C++ libraries from C++ itself.
      - erichocean 2mo ago
        I mean if you're going to be that pedantic, then Clojure is "native" since all Clojure functions "compile to machine code" via the JVM's JIT.
        deleted 2mo ago
        [deleted]
- yogthos 2mo ago
  I'm also working on Jolt which uses Chez Scheme as the compiler. https://jolt-lang.github.io https://jolt-lang.github.io I've already got enough of JVM compatibility to run Ring apps, and have some fun libraries like a Reagent style library on top of GTK https://yogthos.net/posts/2026-07-02-jolt.html https://yogthos.net/posts/2026-07-02-jolt.html

jlarocco 2mo ago

On a related note, there's a cross-platform Common Lisp package, "Bike" https://github.com/Lovesan/bike https://github.com/Lovesan/bike, that lets you use .Net assemblies from Common Lisp. I've used it a tiny bit at work (on Windows) and at home (on Linux), and ran into one issue with "out" parameters, but otherwise it works really well.

nobleach 2mo ago
That's just crazy! (in a good way) I've been in software since 1998 and it's like I've just uncovered a whole new world.
- vindarel 2mo ago
  What about this one? https://github.com/dotcl/dotcl https://github.com/dotcl/dotcl > Common Lisp implementation on .NET. Lisp source is compiled to CIL (Common Intermediate Language) and runs on the .NET JIT — so the same Lisp image runs on Windows, macOS, and Linux across x86-64 and ARM64 without per-platform porting work.
  - jlarocco 2mo ago
    Thanks! I don't think I've seen that one.

arikrahman 2mo ago

Now there's Jank too, the first time a Lisp dialect has reached into native world since Clasp. The way it interops Clojure with the LLVM is unprecedented.

Jtsummers 2mo ago
> the first time a Lisp dialect has reached into native world since Clasp. What's that supposed to mean? Many (probably most if we only consider the non-toy ones) lisp implementations are "native" (compiling to native machine code, not interpreted).
- erichocean 2mo ago
  You can directly call C++ as C++, not via a C ABI.
  - Jtsummers 2mo ago
    > You can directly call C++ as C++, not via a C ABI. That's a unique definition of "native". It suggests that C is not a native language, which is going to be a hard thing to convince others of.
    - didibus 2mo ago
      Ya, I think that was a bit misspoken. They mostly meant direct C and C++ interop. It feels much less like a traditional FFI and more like using C and C++ libraries from C++ itself.
    - erichocean 2mo ago
      I mean if you're going to be that pedantic, then Clojure is "native" since all Clojure functions "compile to machine code" via the JVM's JIT.
      - deleted 2mo ago
        [deleted]
yogthos 2mo ago
I'm also working on Jolt which uses Chez Scheme as the compiler. https://jolt-lang.github.io https://jolt-lang.github.io I've already got enough of JVM compatibility to run Ring apps, and have some fun libraries like a Reagent style library on top of GTK https://yogthos.net/posts/2026-07-02-jolt.html https://yogthos.net/posts/2026-07-02-jolt.html