Q1 2020 Funding Announcement

Clojurists Together is happy to announce that for Q1 of 2020 (February-April) we are funding four projects:

Recap

For those who are new to Clojurists Together, our goal is simple: Fund critical Clojure open-source projects to keep them healthy and sustainable. Clojure companies and individual developers sign up for a monthly contribution, and we pick projects to fund each quarter. Previously we have supported datascript, kaocha, cljdoc, Shadow CLJS, clj-http, Figwheel, ClojureScript, CIDER, Aleph, Neanderthal, Fireplace, and other projects.

Funding details

We support our grantees by paying them a total of $9,000 over three months ($3,000/mo).

Reagent

Why is this project important to the Clojure community?

Based on Clojars downloads Reagent is the most used ClojureScript React wrapper. Reagent is also one of the most popular ClojureScript projects on GitHub with 3.7k stars, and re-frame, a framework built on top of Reagent has even more stars.

What are you wanting to achieve with this funding?

I can work on Reagent at work, during our 10% time and in some cases during customer projects, but this is mostly maintenance and small fixes, as it is hard to find time for bigger changes.

To implement larger changes I’d need some weeks of dedicated time. Two of the bigger changes I’ve been thinking about are:

One of the most asked features is if Reagent support for React hooks. Unfortunately hooks are only usable with React functional components. and currently Reagent RAtom implementation uses Stateful Component state. RAtoms need to know which components depend on them, and be able to re-render the component when RAtoms change. This should be possible by storing storing state and triggering re-render using hooks. The trick will be implement this in a way that doesn’t break existing Reagent components, which presume stateful components.

As this affects how Reagent turns Hiccup to React elements and components, I have some ideas on allowing users configure the Reagent Hiccup compiler, similar to what Hicada does. This would also allow introducing optional features which would break existing Reagent code, by making users opt-in to these. One case would be to make React component interop simpler.

As hooks is the more important feature, I’d start by testing out the ideas I have for that, and then see if that it makes sense to implement that alone, or if Hiccup-compiler changes are needed/make sense to implement at the same time.

I think a good outcome would be to have Reagent alpha/rc release with Hooks support with the funding, and even better if I also have time to test ideas for Hiccup-compiler feature.

fireplace.vim

Note: Tim has other work commitments for the next few months, and will start work on fireplace once those finish up.

Why is this project important to the Clojure community?

Fireplace.vim was used by 10% of Clojure developers in the most recent Clojure survey.

What are you wanting to achieve with this funding?

Ring

Why is this project important to the Clojure community?

Ring is the most commonly used HTTP abstraction layer for Clojure.

What are you wanting to achieve with this funding?

I’d like to bring out a draft spec and experimental alpha for Ring 2.0, in order to better support asynchronous HTTP connections, and to pave the way to support HTTP/2 and HTTP/3 in future. As a secondary objective, I’d also like to remove the provided dependency on Java servlets from Ring core.

Calva

Why is this project important to the Clojure community?

We’ve seen that Calva helps new Clojurists get up and running with Clojure without having to worry so much about tooling. Perhaps more importantly, VS Code has become such a major platform for developers and it’s important to have Clojure(Script) support in the developers’ editor of choice.

What are you wanting to achieve with this funding?

We would like to add the ability to work with large data sets. Currently, large data sets can freeze up the REPL session, and this makes Calva unusable for some developers who routinely work with such data. We would also like to add Clojure debugging to Calva. These are the two main goals, but handling large data sets is the priority. If at any point one of these problems seems to require a lot more time than we anticipated, we may shift our focus to handling the one task for the duration of the funding period, if necessary. In addition to those goals, we’d like to handle issues here and there and maintain the issue log where needed.

Voting details

The projects that applied this quarter were:

Q1 2020 Funding

We had a bunch of great applications from great projects. If you’d like to see more projects get funded, then please join. If you applied for the last funding cycle, we will re-use that application for future funding cycles. If you maintain a Clojure/ClojureScript project that is important to the community, consider applying for funding so we can help you keep it sustainable.

Lastly, a big thank you to all of our members. We couldn’t have done it without your support.