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.

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.

This year certainly was a productive one for me. I’ve written ~40 posts, have many more in the works, made a few new projects in Fennel and Clojure, and changed more of how I spend my time overall. The last year’s recap I mentioned that I’m no longer available on most social networks - this certainly helps me keep a more healthy mental state.

The title says it all. No, really, I’m astonished at how much software is basically useless without an internet connection. Net is no longer something additional to your daily tasks, it is essential for your daily tasks. Just recently, I installed GSConnect, a GNOME addon that implements the KDE Connect protocol.

I decided to give Janet another look - I’ve mentioned Janet before in this blog, and I have my thoughts on it. However, I have never actually interacted with the language that much - I only read its documentation and some code.

Have you tried using the GNOME Software? This thing: Do you use it? Are you even using GNOME? Oh, sorry, I think should point this out, it’s kinda important - I’m asking the developers of GNOME Software. Because, apparently, they don’t. OK, let’s start this post over.