jank blog

Welcome back!

I've continued my optimization work through May and today I'll be reporting the status of the next benchmark: a little Clojure ray tracer.

Good news, everyone!

Hey folks!

The past two months have been incredibly busy and the jank community has been playing and ever larger role in moving jank toward its alpha release.

If you've wondered how much a solo dev can build for seamless C++ interop on a quarter, you're about to find out.

Two months into seamless C++ interop in jank, what sort of magic can we do now?

Howdy, folks!

This was an April Fools post.

Hey folks!

I did it.

Hi everyone!

Hi everyone!

Welcome back to another jank development update!

Hey folks!

This quarter, I'm being funded by Clojurists Together to build out jank's lazy sequences, special loop* form, destructuring, and support for the for and doseq macros.

Oh, hey folks.

For the past couple of months, I have been focused on tackling dynamic var bindings and meta hints, which grew into much, much more.

One thing I've been meaning to do is build a custom string class for jank.

I've been quiet for the past couple of months, finishing up this work on jank's module loading, class path handling, aliasing, and var referring.

For the past month and a half, I've been building out jank's support for clojure.core/require, including everything from class path handling to compiling jank files to intermediate code written to the filesystem.

As summer draws to a close, in the Pacific Northwest, so too does my term of sponsored work focused on a faster object model for jank.

This quarter, my work on jank is being sponsored by Clojurists Together.

After the last post, which focused on optimizing jank's sequences, I wanted to get jank running a ray tracer I had previously written in Clojure.

In this episode of jank's development updates, we follow an exciting few weekends as I was digging deep into Clojure's sequence implementation, building jank's equivalent, and then benchmarking and profiling in a dizzying race to the bottom.

I was previously giving updates only in the #jank Slack channel, but some of these are getting large enough to warrant more prose.