Clojurians Log v2

Hey folks, in support of the https://www.clojuriststogether.org/news/q3-2026-funding-announcement/, Eve 0.9 is out: one persistent data-structure implementation for eleven Clojure hosts, built on a global blob store - every value in 1 MB linear pages named by CID, written into the writer's own pages, and CAS'd at the atom root — so the same atom lives in memory, on disk, or across the network and only materializes the branches you actually touch. It turns your Clojure into a "cloud language" by letting you move parts of your application and your runtime into globally observable, persistent data. It basically takes the epochally coherent sharing idea in Clojure and makes it a network protocol: https://github.com/SeniorCareMarket/eve Eventually we'll be making this tech available to other languages outside of Clojure. But IMO those languages will just end up looking more and more like Clojure. Eve argues that the same things that makes Clojure better for in language concurrency also make things better for distributed systems - we just need to further embrace immutability and epochal persistence coordination and keep building on this architecture into the cloud. Datomic was one step in that direction but I think we can be taking things further, with an ecosystem of distributed systems that implement these architectural ideas. Fair warning - Eve is currently a very AI driven development project. As such, the bits are very pre-alpha and are not ready for production. Getting eve ready for human consumption will require lots of human effort from actual humans reading the actual code and ensuring that it solves actual human problems the way we want. I have plans to formalize "namespace-level human validation" policies at some point where, for some large point releases, all namespaces that changed since the last release must be eyeball-checked by a human before the next release. But that's only after the bits have started to settle, and we have more humans involved in the "eve standard." Basically, if a bot changes a human-validated ns, it invalidates the ns until the next major release, when it gets another human eye-ball validation check. Head on over to #C0AP53Z8WBG to get involved and learn more!

https://github.com/replikativ/ansatz/tree/main/modules/lean-jvm: run compiled Lean 4 functions on the JVM.

(require '[ansatz.lean.jvm :as lean] '[ :as io])
(with-open [rt (lean/open)
            in (io/input-stream "pricing.leanjvm")
            p  (lean/load-artifact rt in expected-manifest-sha256)]
  ((lean/function p "Pricing.discount") 10000 1500 1000))
;; => 1000

lean-clj: write functions and proofs in Lean 4, call them from Clojure on the JVM. https://github.com/conao3/lean-clj deflean checks embedded Lean (proofs included) at compile time, and a CLI compiles whole Lean modules into Clojure namespaces.

(deflean arith
  (def double [n Nat] Nat (+ n n))
  (theorem double_eq [n Nat] (= (double n) (* 2 n))
    (by (unfold double) omega)))

(double 21) ;=> 42