Clojurians Log v2
announcements 2026-10-19
Nice one. No manual option as far as I can see?
correct, no manual option
That's really great, thank you!
On mobile (Android Firefox Beta) the menu button in the top right does do anything when pressed. Is it supposed to do something?
Ah, the menu doesnt seem to do anything on firefox or chrome (when screen size is small). I assume if the menu was working it would show links for "Core Library", "Quick Ref", "Login"
Dark screen is working very well on both Firefox & Chrome (on Linux & android). Thank you for the work making it happen.
I'll take a look at the "hamburger" button on mobile
I made a test runner that runs tests in parallel and has interactive feedback, inspired by vitest: https://kirahowe.com/2026/oct/19/introducing-volley It should run with minimal changes on any test suite that was already using kaocha (because that's mostly what i was using before) and for now only works with bb and JVM Clojure. Lots of rough edges still and I'm working on many improvements, but I'm using it on all my projects now so figured it's at least worth putting out there, with all the usual caveats of alpha libraries. Let me know if you try it out and have any issues or feedback!
what's the benefit over eftest? that it's built with kaocha integration?
That's not the main benefit. It's mostly in the architecture and user interface. eftest parallelises with threads in one JVM, so tests share global state (with-redefs, atoms, dynamic vars etc) and you mark the unsafe ones synchronized. volley runs namespaces in separate worker processes, so they can't interfere with each other's process state. It also runs on babashka natively (which is mostly what I built it for). It also has a watch mode that reruns only the namespaces affected by a change. By kaocha compatibility here I just mean that existing kaocha users can switch very easily by just changing one command -- flags and config should mostly just work. If you're writing JVM Clojure with thread-safe tests, eftest is a great choice and has less startup overhead.
and by "user interface", I meant the terminal output. It's inspired by vitest, I like the realtime reporting, it looks like this (on volley's own test suite): https://github.com/kirahowe/volley/blob/main/doc/volley.gif
very cool
i'm hoping to add parallelization to lazytest next year, i'll def be looking to your work for inspiration
wow, it's test runner day today. thanks for making it bb compatible. @teodorlu also made a thing: https://github.com/teodorlu/deltatest maybe there are ... parallels?
Nice! It appears volley's speedup (parallelization) and deltatest's speedup (persistent JVM for test runs, skips tests that aren't impacted by latest changes) could be combined.
This is great.
https://github.com/clojure/clojure-cli.repl is now available.
As this new REPL continues to evolve, I wanted to bring it closer to my editor workflow. While editors commonly connect to a REPL, the output is displayed somewhere else. What if instead evaluations sent from your editor showed up in the terminal REPL with their namespace, code, and output? This release supports connecting https://github.com/clojure/clojure-cli.repl/blob/main/doc/editors.md to the REPL server. You can then open editor results in the https://github.com/clojure/clojure-cli.repl/blob/main/doc/inspector.md.
This release has a few other features as well:
* TAB https://github.com/clojure/clojure-cli.repl/blob/main/doc/configuration.md#completion
* https://github.com/clojure/clojure-cli.repl/blob/main/doc/configuration.md#init to run a function once at server startup
* Emacs-like https://github.com/clojure/clojure-cli.repl/blob/main/doc/configuration.md#key-strings in key bindings: C-x d, C-M-f, C-x chords, including common https://github.com/clojure/clojure-cli.repl/blob/main/doc/editing.md
* Colors are now compatible with Solarized themes
Follow up discussion is welcomed #C0C5YK5PAQ0
If I wanted to extend this to another editor (vim, vim-fireplace) what do I need to look at? An nrepl middleware? It's automatic anyway?
It's standard nREPL but adds a couple of ops for its own client. I use it with CIDER, Portal, and Rephrase middleware.
@dominicm there is a very good chance it works as is with fireplace (although I haven’t tested it myself). There is no additional middleware required. Try it out and if it misbehaves (or if it does work) drop a report in #C0C5YK5PAQ0
Same steps as with the others clojure -M:repl and then opening your editor in the project you should see the evals appear from fireplace.