Wave

I went and created a tiny HTTP-fetching Clojure program called wave (see, it’s like a curl…) that fetches URLs given on the command line and dumps the results to the console. It can do HTTP/1.1, HTTP/2, and HTTP/3. It works interpreted and as an AOT compiled binary.

It uses tools.cli for command line parsing, which took a little bit of porting to get it to run on cljrs. It also helped me find and fix a heap of bugs in cljrs—everything from wrong command line argument handling to wrong code generation.

No code survives contact with a user. like pausing to try out some software I’m working on, to run it or break it and expose the rough edges.

Zeta

I have enjoyed playing around with cljrs and seeing what’s possible to do with it. The latest thing I’ve tried is a website that lets you play around with the Riemann Zeta function. It’s a beautiful, intriguing function to play around with, because it very likely has

Hammock Oriented Development

It would probably be a point of contention the main way I’ve been working on Clojurust recently: that a lot of the coding is done by Claude Code, with less and less of my own direct involvement. I’m not interested in defending doing this kind of development, and

Stressed

I had put together a stress test of Clojurust, which just runs all the tests currently in the repo, both under AOT compilation and the direct interpreter/JIT path. Some recent interpreter GC-rooting fixes landed, and the stress test just had its first successful run. It's a

And honey, us the fable

So there was a brief period where I had Fable access, and it was at the same time incredible, frustrating, and expensive. When I use Claude Code, I like to have it write a clear plan about the big picture I want to tackle, and once that’s done and

Read more

Zeta

Hammock Oriented Development

Stressed

And honey, us the fable