I attended a Processing Jam this week!
Processing is a flexible software sketchbook and a language for learning how to code. Since 2001, Processing has promoted software literacy within the visual arts and visual literacy within technology. There are tens of thousands of stude…
The discussion evolves
I'm back with another report on investigating core.async in Trunk. My thread on clojureverse has evolved quite a bit, …
After fuddling about with Core.async in Trunk I decided it was time to reach out for some input. It was a good thing I did; I had reached a point where I was mostly poking at the functions I thought I understood in core.async, and wasn't really reading their API.
I'm thinking about re-writing my static site generator for Org-mode (Firn) from Clojure to Rust. I'm not sure if I will do it, but I've been thinking about some of the more fundamental design decisions that I want to consider when building software. Firn is built in Clojure, with a touch of Rust for the Org-mode parser, and then is all compiled down to a binary using GraalVM's native-image tool. It's working, so why re-write it?
I would really like to better understand Core Async with Clojure; specifically, I want to remove myself from callback hell to see if I can make my Clojurescript backend for a new project a bit clearer.
My latest project is called Trunk. It's a tool inspired by an application called "Learning with Texts". Rather than go into what it is (see the wiki page), I'll talk a bit about the technical aspects of the project and why I decided to pursue it.