Nov. 2026 Short Term Project Updates

By Kathy Davis

Here are the first updates for projects funded in Q3 2026. You can find overviews of these projects in the original funding announcement. There is a lot to dig into here - Thanks everyone!


Design Services for Key Community Projects: Jeremiah Coyle

Q3 2026 $9K Report 1. Published November 1, 2026

Focus for October 2026:


Squint Playground UI Updates, Part 1

PR #989

phase-1-before-after-white


Squint Playground UI Updates, Part 2

PR #1045


All features and fixes included are described in the sections below.


Global layout and framing refactor

Fixes:

Before:

Before: global layout and framing refactor

After:

After: global layout and framing refactor


Draggable resizing of editor and compile panes

Draggable resizing of editor and compile panes



Compiled code section visibility toggle

Compiled code section visibility toggle




Support codemirror dark theme across editor, repl output, and compiled code instances

CodeMirror dark theme across editor, repl output, and compiled code instances



Respect OS color scheme for initial theme state

Respect OS color scheme for initial theme state



Native tooltips optimized for light-dark themes

Native tooltips optimized for light-dark themes




Unified text selection styling

Unified text selection styling



Misc



Squint Playground UI Updates, Part 3

PR #1056

This introduces a more flexible layout for the Squint playground.


Layout


Global layout

Before: Two panes, with the controls in a row at the top of the output pane.
After: Example menu above the code pane, Compile and Share above the output pane, and a footer.

Before: Two panes, with the controls in a row at the top of the output pane. After: Example menu above the code pane, Compile and Share above the output pane, and a footer.


Code pane

Before: Editor only.
After: “Select example” bar above the editor.

Before: Editor only. After: "Select example" bar above the editor.


Adjustable DOM frame

Resizing the DOM frame from its side, bottom and corner handles: Resizing the DOM frame from its side, bottom and corner handles


DOM layout options

The DOM frame can now go in 3 different positions:

Layout selector in footer: Switching the DOM frame between above the panes, the output pane section and full screen

Switching the DOM frame between the top pane, the output pane section, and full screen: The DOM frame above the panes, in the output pane section and full screen


Output pane


Before: Buttons in a row, REPL-mode checkbox and “Compiled code”.
After: Control bar, then REPL-mode and Compiled JS sections.
Before: Buttons in a row, REPL-mode checkbox and "Compiled code". After: Control bar, then REPL-mode and Compiled JS sections.


Collapsing and expanding the REPL-mode and Compiled JS sections: Collapsing and expanding the REPL-mode and Compiled JS sections


Example menu


Opening the example menu and picking an example: Opening the example menu and picking an example


Error Slot

Runtime errors were being rendered into the REPL result box, which is meant for the value of the evaluated form, and it is hidden when REPL-mode is off. So an error with no source location, such as a module that fails to resolve, was invisible unless user opened the dev console. Errors with a location still got an underline in the editor, but nothing told you what went wrong.

Errors now have their own slot in output pane, below the Compiled JS section:

Errors thrown later, from event handlers or animation frames, still only appear in the dev console.

Example error from unresolve module: error-slot-white

Examples


Pinball table example, upgrades

The new pinball table in dark mode


Advent of Code


Misc




ECA docs site updates, phase 0

This is a lightweight first pass. It covers some basic typography, legibility, icons, sidebar and table of contents styling, and layout cleanup on the homepage and install page. It also sets up a visual changelog in docs/evolution/changes to track ui changes going forward (optional).

Summary of the main things that were changed, detailed in the sections below:

Screenshots compare the last commit (before) with the working tree (after), both built with mkdocs-material 9.6 at 1440x900.


Documentation page typography



Docs page

Before: Roboto typeface and accent (teal).
After: Inter typeface and neutral.
Before: Roboto typeface and accent (teal). After: Inter typeface and neutral.



Article

Before: Accent (teal) headings and links.
After: Inter typeface and underlined links.

Before: Accent (teal) headings and links. After: Inter typeface and underlined links.




Before: Accent (teal) and flat.
After: Indented with rule.

Before: Accent (teal) and flat. After: Indented with rule.



Table of contents

Before: Accent (teal).
After: Indented with rule.
Before: Accent (teal). After: Indented with rule.


Homepage icons and feature cards



“Why ECA?”

Before: Emoji icons.
After: Lucide icons.
Before: Emoji icons. After: Lucide icons.



Feature cards

Before: Emoji icons and stacked.
After: Lucide icons and two columns.
Before: Emoji icons and stacked. After: Lucide icons and two columns.



Config tabs

Before: Emoji icons.
After: Lucide icons.
Before: Emoji icons. After: Lucide icons.


Install page



Install page

Before: Centered intro.
After: Left aligned.
Before: Centered intro. After: Left aligned.



Install intro

Before: Centered and narrow.
After: Left aligned and full width.
Before: Centered and narrow. After: Left aligned and full width.



Plugin copy

Before: One paragraph.
After: Two paragraphs.
Before: One paragraph. After: Two paragraphs.



Manual install

Before: Collapsed toggle click target is too distant, small, and faint: the user may miss it.
After: The instructions are always open and visible. Reduced noise on the section heading.
Before: Collapsed toggle click target is too distant, small, and faint: the user may miss it. After: The instructions are always open and visible. Reduced noise on the section heading.



Help

Before: Centered sentence.
After: Bulleted list with aligned hyperlink styling.
Before: Centered sentence. After: Bulleted list with aligned hyperlink styling.


Protocol page arrows



Protocol headings

Before: Emoji arrows.
After: Text arrows.
Before: Emoji arrows. After: Text arrows.


Misc

Header, homepage hero and footer keep their original accent (teal).




ECA docs site, phase 1: persistent docs sidenav

The left menu now shows the whole docs map on every page, and the left menu and the table of contents share one set of styles.


Top bar



Both menus, the left menu and the right-hand table of contents, use the same styles.



Persistent documentation sidenav



Configuration open with the current page highlighted, the other items plain links:
Configuration open with the current page highlighted, the other items plain links



“On This Page” (formerly “Table of Contents”)



Wider menu with the current entry highlighted



Misc



Tablecloth: Ethan Miller

Q3 2026 $9K Report 1. Published November 1, 2026

Overview

This grant continues work on Tablecloth’s Column API that I added in 2022 thanks to a previous Cojurists Together grant. The Column API is the part of Tablecloth that lets you work directly with columns (math, statistics, missing values) rather than whole datasets. My three goals for the current grant are designed to solidify and enhance this API within Tablecloth. They include:

  1. A fuller tutorial that showcased what the Column API can do and when it comes in handy.
  2. Making the code generation behind the Column API more transparent and easier to work with.
  3. “Lifting” more operations from the lower-level processing library dtype-next into the Column API.

Much of both the Column API and the Dataset API is produced by a code generator: templates that write out the public functions so we don’t have to write hundreds of near-identical wrappers by hand. Before writing a tutorial or adding more operations, I wanted that machinery to be easy to run, safe, and checked automatically, because every later change depends on it. So October went mostly into goal 2.

Planning and community

Code generation work

Merged: Column API no longer loads the whole Dataset API (#220) The Column API’s missing-value code pulled in the entire generated Dataset API just to use two small helpers. Now it requires only those helpers. Loading the Column API is lighter, and regenerating it no longer drags in unrelated code. Behavior is unchanged, and a new test guards against the dependency coming back.

In review: one command to regenerate everything (#221) Regenerating the four generated API files used to mean opening the source and evaluating four separate comment blocks by hand. Now a single command, clojure -M:regen, does it all:

In review: CI check for stale generated files (#222) Until now nothing stopped a hand edit to a generated file, or a template change without regenerating, from being merged unnoticed. This adds a check on pull requests that regenerates the files and fails if they differ, naming the stale file and telling the contributor to run clojure -M:regen. It is read-only, so it is safe to run on pull requests from forks.

In review: generated code no longer loads the generator (#223) Every generated column operator called a helper that lived inside the code generator, so using Tablecloth at runtime also loaded the build-time generator. Some generated namespaces also relied on other namespaces they never required, which only worked because the generator happened to load them. This moves the helper to a runtime namespace and makes each generated file require exactly what it uses. The public API is unchanged.

Docstring audit I audited the docstrings in the generated APIs. That turned up several problems, which I’ve ordered into follow-up work for November:

Lag and lead

lag and lead shift a column’s values up or down, which is common in time-series work (comparing each value to the previous one, for example). I first improved these in tablecloth.time (#67):

I’m now bringing a lag function built on the Column API into Tablecloth itself.

Next month



EVE (Extended Value Encoding): John Newman

Q3 2026 $2K Report 1. Published November 20, 2026

eve is a persistent data-structure library - maps, vectors, sets, lists, etc, that live in shared memory as atoms. It’s implemented in .cljc, so it targets over a dozen clojure-likes. Clojurists Together funded eve this quarter and my goal was to improve the Clojure impl (the cljs version came first), improve the docs and get the library to a 1.0 status. I feel like we’re half way there.

The tl;dr:

There are three new demo apps showcasing eve’s abilities - eve.db.ds, the cohost media demo, and narcis.

One implementation, ten hosts

So our current line-up is:

JVM Clojure, ClojureScript on Node and in the browser, Babashka, nbb, ClojureCLR, Basilisp, Jolt, clojerl and Glojure - with jank and ValueScript support soon. Jank basically works but there’s still some wrinkles I have to iron out.

The code base is now much more uniform as cljc across all the target platforms. It will take a while to sort out what the best common abstractions are for the various clojure-likes to plug into, but as it evolves I hope the shape helps inform how the community might increase the scope and functionality of the default cljc experience in the future.

Atoms that cross processes and networks

We’ve got some tests going with writers from eight hosts banging on a disk atom under contention safely. We have Rich Hickey’s ant demo running in the terminal, with hosts from different runtimes running agent ants together on a grid of refs living as atoms on disk. It’s all coordinated by STM between the runtimes over the disk atoms in a leaderless and permissionless way, lockfree and with optimistic updates. STM also works over network atoms - I’m calling that NTM - network transactional memory! Not as much testing has been done there yet though. More to follow there next update.

Durability and memory

We have a 72 point crash suite to stress test our journaling behavior. It actually increased speed. For workloads like incrementing counters we’re going 1.62x before. The journal allows the threads to optimistically run ahead a little bit. We do go 15 to 25% slower under contention though.

We also brought back allowing for multiple atoms under one domain, which allows you to share memory between atoms of a single domain. However, doing so requires tracking mutual ownership with regard to retirement and epochs and the journal, which brought the perf hit under contention. We removed reflection from the JVM’s memory access and made a counter swap 10x faster. Disk atoms are tiered atoms: the in-memory tier is a cache over the disk tier, so an atom that grows past resident memory spills to disk instead of failing. For network atoms, the disk becomes a second, larger cache tier that spills over to the network. In principle, there is no need to have a logical limit on the memory size of an eve atom. Therefore, the address space for eve atoms has been made deliberately future proof.

Data formats and flat values

Murmur is out of both hash and HAMT key placement and wide hashes now agree on JVM and ClojureScript. A #char reader tag (codec tag 0x14) landed so character values round-trip across hosts.
In the 0.9.1 release, instantiating eve data outside of an eve transaction would throw. Now it automatically produces a flat variant - a lean Valhalla-like value form with no identity of its own. The flat machinery is one portable implementation, and the documentation now describes Eve’s two value types, persistent and flat, side by side. More to come on this.

Seeing it run: the media transcoding app and narcis

To show how eve can make an application “stateless” with respect to RAM, I forked Burin’s Jonquil and made narcis. It lets you edit very large code bases while keeping the runtime state of your editor durable, even surviving machine restarts:

Narcis

(narcis text editing app, based on jonquil)

The cohost media editor shows how you can fuse multiple clojure-like runtimes together to create a media transcoding app - runtime fusion. In my opinion, it’s quite ugly, but that’s not the point! The idea is to show how the different runtimes are working together:

cohost v2

(Cohost Media Example App)

And here’s the ant demo running from the cli:

ant

(A CLI ant demo, based on Rich Hickey’s)

What’s next

There is a lot going on over here, but the bits are starting to settle and I’d love to have folks poking at eve. Sorry again for the delayed update. I would also like to figure out a development process that integrates human checks on critical namespaces and functions for large point releases. I’m not sure if I’ll have something together by the end of the funding period but I’ve been hosting some conversations about it with the community.

Thanks to Clojurists Together and its supporters for funding this work! (edited)


Finish Carmine 4: Peter Taoussanis

Q3 2026 $2K Report 1. November 16, 2026

Hi folks! 👋

Making good progress on the upcoming release of Carmine v4 (next gen Clojure Redis client). Am hoping to release alpha1 for early testing/feedback later this month (November).

The last few weeks have been focused on refinement: last passes on the UX/API, documentation, performance tuning, and lots of testing.

I’ve also been backporting improvements where possible to the v3 line (see the recent v3.6 and v3.7 releases for example).

What to expect

Testing + feedback

Once alpha1 is out, next step will be testing and feedback. Particularly hoping for folks to try out the new systems like Sentinel, Cluster, and the new Pub/Sub API.

These involve the most tricky decisions and interactions, so will also need the most scrutiny.

My hope is to aim for something like beta1 before the end of the year / early next - depending on how many folks are available to help test. Feel free to ping on GitHub if you’re interested 👍

Wrapping up

It’s been a long, multi-year road - but almost there now. Looking forward to announcing the first alpha soon. Cheers! 🫶

- Peter