Clojurians Log v2
announcements 2026-04-12
In preparing Calva calva for the Clojure Documentary success, the latest release, https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.573, makes a long overdue update of defaults for the REPL UI, harmonizing these defaults with the various starter projects that Calva can create. And we also switch out the mini Clojure project starter for the https://github.com/clojure/try-clojure project. This creates an even straighter path From Zero to REPL than what even https://www.youtube.com/watch?v=huGyv5yLIM8&list=PLZdCLR02grLrV9DixP5NEMT7gNaUWMIOl has it. Basically, install Java, VS Code, Calva -> Try Clojure, BOOM!
Changelog:
• https://github.com/BetterThanTomorrow/calva/issues/3166
◦ Use terminal as the default destination for all output categories
◦ Echoing of the evaluated code to the output evaluation result destination is now default enabled
◦ The configured output evaluation result destination will unconditionally always show code evaluated via the API (such as when Backseat Driver evaluates things)
◦ Don’t auto-reveal the Calva Inspector at REPL comnect
• https://github.com/BetterThanTomorrow/calva/issues/3168
Feedback here, in #calva, and in #backseat-driver super welcome! 🙏
Looks like so, once Java, VS Code and Calva are installed:
Good to know: Calva is prepared for bundling about any project for this kind of quick start. Please let me know if you have a project you think should be bundled. (As of this writing it is still a matter of updating an index in the Calva source code. But if we hit the nice problem of this not scaling we can fix that, making it fully dynamic using an external repo.)
> Echoing of the evaluated code to the output evaluation result destination is now default enabled
I just updated to this latest version of Calva and when I eval code to a connected REPL, I do not see that code echoed. Sure enough, I have that option already set to false but don't remember making that change. Is it possible an older version of Calva might have added that setting as false at some point in the past, or must I have set it false manually and just don't remember?
Just kinda curious how many folks will actually see a change of behavior here...
If you edit songs using the JSON editor it pastes the default when it completes a setting. So you could have completed that setting looking for something else and not noticed. For someone who really haven’t touched defaults, they will change.
Since you run with these particular setting false, it could be good to know that Copilot will still see the evaluated code echoed, and iirc, you will see all Copilot’s evaluations echoed.
I'm actually quite nervous about the change of these defaults, tbh. There’s a reason I’ve been saying for two years now that they should be changed, and I have not done it… Here’s hoping it won’t be too disruptive for people used to, and using, the old defaults.
> So you could have completed that setting looking for something else and not noticed. Ah, that could well be it, yes. It's easy enough to find and change a setting in VS Code. I wouldn't worry too much about a default like that.
Following up on my earlier announcement of the https://grid-coordination.energy Clojure libraries — two new things:
1. https://github.com/grid-coordination/clj-oa3-vtn — A production OpenADR 3.1.0 Virtual Top Node (VTN) server in Clojure. Two-port architecture (BL + VEN), MQTT notifications via Mosquitto, DynamoDB or in-memory storage. Built on https://github.com/mpenet/legba (OpenAPI spec → Ring routes), https://github.com/stuartsierra/component, and the https://github.com/grid-coordination/clj-oa3 entity library. Routes are derived directly from the OpenADR 3 spec — no hand-written endpoint code.
2. https://github.com/grid-coordination/price-server-user-guide — A live, public electricity price service at