Jolt Runs Clojure Without the JVM and Binds C Libraries Natively
Jolt – Clojure that speaks C
Jolt is a self-hosted Clojure implementation built on a portable Scheme layer, running natively on Chez or compiled to JavaScript via Gambit. Most Clojure code runs unchanged, including persistent data structures, transducers, multimethods, and core.async on OS threads. A native C FFI turns C functions into ordinary Clojure functions, and jolt build produces a single standalone binary with dependencies statically linked. The compiler is written in Clojure and compiles itself.
The compiler is written in Clojure and compiles itself; Chez runs interpreted and compiled code identically, so the REPL and a built binary behave the same.
- giancarlostoro
Curious how it compares to Jank which is also Clojure but for C++.
- christophilus
Well, I think this looks nifty. Yogthos appears to be the author, and he’s done a lot for the Clojure community over the years. I’m definitely going to give this a spin.
- skydhash
Was initially interested (I like languages that binds easily to C because of the nice libraries there, and I'm a fan of LISP), but the README is LLM-generated and the Makefile is unreadable. The there's this part in the AI policy
It is simply not feasible for humans to keep the entirety of large projects in their heads all at once. When working on a project, one is constantly forgetting and relearning code along the way. The situation is even worse for projects where multiple people work together and no one knows what everyone else was thinking. We look at the code and try to build up sufficient context in our heads to make the necessary changes. When we misjudge that context or misunderstand existing code, we end up making mistakes.
It's a made up excuse because no one has ever tried doing that. Instead the core activity of software engineering (and engineering in general) is to break down things into modular components, ensure that they work well, produce specs, then assemble the result. Which is why no one read the source code for open(2) system call before using it. Instead they read the manpage and only when there's an issue there's a need to compare the specs with the implementation.
So it's a matter of communication between humans. If person A is responsible for module 1 and person B's module 2 depends on the former. It's up to A to provide a proper spec to B. It's not up to B to learn everything about module 1's implementation and doing so is kinda foolish.
So som […]
- ivanjermakov
Yet another project named Jolt?
https://github.com/jrouwe/joltphysics