A while ago, I made a library for asynchronous programming in Fennel. It’s based on Clojure’s core.async vision of asynchronous programming using only channels. As an experiment, I’ve added a TCP support layer in that library, allowing one to create a TCP channel, and use it in the same way as a regular channel.

So, here’s a question - when were you last excited for a new phone? Well, I mean really excited? Here’s the thing. Phones are so boring today that most retail stores show you the backside of the phone. Because from the front they all look exactly the same.

I’m not sure if this is a new thing or not, and I’m too lazy to look it up as it’s 3 AM right now, so here it is. I’ve been thinking about state machines lately, and how Clojure’s multimethods are a cool way to implement a state machine.

For quite a long time programming was my main hobby. I enjoyed it, as I felt like I was creating something (hopefully) useful, and the problems I tried to solve were making my brain-cogs turn. However, recently it seemed to change, or at least, I’m feeling my usual burnout a bit harder than usual.

There was a weird thought going over and over in my head, regarding my Emacs configuration, and it extends to the other projects I do both at home and at work. You see, my configuration is riddled with custom code, and up until recently I had mixed feelings about that.

Maybe I’m “beating a dead horse” here, but I haven’t thought about programming languages in this particular way before, so I decided to share the thought anyway: Most programming languages I know are designed like it’s still 80’s, and all we have are textual interfaces, and single-core CPUs.

I’ve been working with Clojure professionally for four years now, and I made some posts about the language in the past. Clojure is a great language, although not without its fair share of things to consider. In other words, I don’t see Clojure as an ideal language by any means, and it’s not suitable for every type of project.

Inspired by some other blogs I decided to do small posts about books I read. I’m not sure if I’m going to do it monthly, or not in a regular way, so we’ll see. “Crafting Interpreters” by Robert Nystrom I already made a series of posts about this book, so I’ll be brief, I’m sure you don’t want to read another ~113 minutes of impressions and sloppy code.

The unexpected part! I liked hacking on Lox in Zig a lot, so I decided it would be great to make some changes to the language. It should be good for a better understanding of the book’s material, and probably will be a lot of fun!

This is a second post about the Crafting Interpreters book by Robert Nystrom. In the first post, I’ve described my experience with the first half of the book, and the challenges of using a different language with different idioms and practices. This post will be no different, although I have a bit more to discuss, and the contents aren’t actually ~2-year-old weak impressions and remembrances.