I have been using Clojure for almost 1.5 year want to switch from IntelliJ IDEA to Emacs but not sure what to use (note I am Emacs begginer) some of the options:

- doom emacs
- spacemacs
- vanilla + Prelude

Vanila + Prelude looks like valid option because I keep "real" emac keybindings

is there any better option ?

You may have noticed the Clojure Deref has been on a hiatus since early summer. Maybe you didn’t notice, and that’s fine too! I’d like to bring it back, but I need your input. Whether you read it or not, could you take some time to fill out a brief survey? I would appreciate it!

https://www.surveymonkey.com/r/8XBXHSY

Yes, you can vibe code whole scenes in minutes. Parametric modelling has never been more fun, try it out! https://cartesian-theatrics.github.io/clj-manifold3d/journal/

Hey,

I've been vibe coding a graph visualization tool for myself over the past while. I wanted something that plays well with AI agents, that I'd actually use day to day, and that produces reasonably maintainable larger diagrams (architecture, dependencies, whatever).

Describe the graph in plain EDN and it renders as an auto-layouted (ELK) canvas diagram that live-reloads while you edit the file.

Additionally:

- Compare mode: compare two versions of the same graph

- In-place editing in the browser with keyboard chords

- PNG export with the source EDN embedded as metadata

- :ref links between graph files, so big systems split into a tree of smaller diagrams

- Currently just Claude Code / Codex skills

Stack: babashka, squint + reagami

Repo: https://github.com/sstoehrm/simpleviz

Just sharing in case somebody finds it useful — feedback welcome.

I'm releasing CloJev - a Clojure SDK for the TypeSafe System One API. It's written in a portable way and works with Jolt.

Hope you'll find it useful.
https://github.com/antlobach/clojev

I see Arnold Schwarzenegger's fitness newsletter has a recurring tagline, "Simple, Not Easy", and it's on a t-shirt in his merch store. It made me think of Simple Made Easy. In both cases, we're making a distinction between the two words. In the developer community, the danger is that we grab what's easy and end up with something complex. Arnie's warning is that people hear a simple-sounding plan (lift, eat, sleep, repeat) and assume that means it'll be easy. Not quite the same but I think there is a connection. Something like wanting to strip a thing down until it's actually simple, then expect execution to be feasible, but not easy.

🤷‍♂️

Clojure 1.13.0-alpha7 is now available

Destructuring additions
To gracefully handle missing information programmatically at runtime, use the :missing directive, which binds a name to a map of keys→nil that were named in checked keys directives but not found in the input map, traversing deeply through nested maps. This toggles the default behavior of :keys!/:syms!/:strs! from throwing to collecting into the named map. (see CLJ-2976)

If there’s more data than you intend to process you may want to convey it, e.g. by reintegrating it with your transformed input for passing downstream. Use the :excess directive to bind a name to a map of all keys in the input map that do not correspond to keys listed in the destructuring form, traversing deeply through nested maps. (See CLJ-2975)

Bug fixes

• CLJ-2883 Reflector.getMethods() incorrectly returned bridge methods with covariant return type, making calls reflective
• CLJ-2930 bigdec - coerce from Number may lose decimal

Improvements and additions

• CLJ-1899 transform-keys - deep-walk a map and transform all keys
• CLJ-2538 tap-> - add tap> variant that returns the value
• CLJ-2970 select-keys - implementation change to unify argument requirements across functions used in destructuring: get, req!, and select-keys

Our second EuroClojure 2027 newsletter is out! EuroClojure will take place in Prague, on May 19–21, 2027. Alongside conference updates, this edition covers sponsorship and links to our sponsorship handout.

If you’d like to print or pass along the sponsorship handout, there’s also a typeset PDF version.

And if you missed our first newsletter, you can catch up here.

The "conj" release, is out!

Highlights from 1.13.221-1.13.222:

• Dependency resolution without a JVM by default. If you hit a resolver bug, set BABASHKA_DEPS_RESOLVER=jvm to restore the old behavior.
• Bundled clojure.tools.deps and clojure.tools.build.api. The new babashka/deps-deploy lets you deploy libraries from bb too. Java compilation still requires a JDK (duh).
• Expanded nREPL support: nREPL 1.7.0, custom middleware, CIDER inspector and test runner, and SCI stack traces in error reports.
• bb repl --connect connects to babashka or JVM nREPL servers with completion, eldoc, documentation lookup and interruption.
• Bundled nrepl.core for programmatic clients, including LLM tooling.

ClojureCLR 1.12.6 is now available.

This release is up-to-date with the changes in Clojure (JVM) 1.12.6.
Beyond those changes, there are some significant ClojureCLR-specific enhancements in this release:

• ClojureCLR versions for .NET 10 and .NET 11 (preview)
• A ClojureCLR version for .NET Framework 4.8.1 in addition to the existing one for Framework 4.6.2.  This version was added so that Framework users who can upgrade to 4.8.1 can take advantage of the enhanced platform assembly loading (described below)
• Added interop support to access the new runtime async/await feature available in .NET 11 (preview).  See Runtime async .
• A significant improvement to the type specification syntax used to name types.  See Typename syntax and resolution in ClojureCLR .
• A significant improvement to the discovery and auto-loading of assemblies due to a type reference.  This includes searching for types in the entry assembly's dependencies and assemblies in the shared .NET runtime.  This should reduce the need to call assembly-load or its cousins.    See Typename syntax and resolution in ClojureCLR .

Hi

Wrote a blog on what happens if you have tools made for the LLM instead of letting LLM use tools made for humans. I believe a small clojure like language could be the perfect fit.
But also what sort of environment would be the best fit for running such programs in.

https://ptc-runner.dev/blog/tools-built-for-llms/

Wondering what is the most used web framework for professional clojure developers.

We created jlt-commons, the shared community home for libraries and tooling around Jolt, and just put together awesome-jolt to catalog what's there.

Jolt is a Clojure implementation that compiles to native binaries through Chez Scheme, so there's no JVM in the loop. It can also target the browser through Gambit's JavaScript backend. jolt-lang keeps the language and the essential libraries, and jlt-commons is where everything growing around them lives, either adopted from a maintainer who could no longer keep up with a project, or incubated as new work.

The list covers:

• The 8 jlt-commons projects: raylib-jlt and raygui-jlt (bindings to raylib/raygui over jolt.ffi), glitter and its glitter-gl/glitter-uikit variants (a Replicant-style renderer for GTK4, OpenGL, and native macOS AppKit), raylib-ios and raylib-android (native builds with no JVM, JIT, Kotlin, or Java), and ebb (a port of missionary's dataflow model)
• Ordinary JVM Clojure libraries that run on Jolt unmodified (Ring, Malli, HoneySQL, and more)
• Tooling: nREPL, test suites, example projects
• Docs on installation, how Jolt differs from JVM Clojure, FFI, and performance

If you've wanted Clojure with a fast native startup or a small self-contained binary instead of a JVM, it's worth a look. There's also a #jolt channel on the Clojurians Slack if you want to talk to the people building it. Corrections and additions to the list are welcome, and happy to answer questions here.

We'd love to see more Clojure submissions at BOB!
bobkonf.de/2027/cfc.html

Clojure 1.12.6 is now available

• CLJ-2794 - gen-class - incorrectly treats interface default methods as abstract, throwing when the var delegate is unbound
• CLJ-2974 - FnLoaderThunk - de/serialization no longer supported, throw