Everyone likes to complain when a build tool “downloads the internet” the first time they check out a new project. But the cost is typically amortized over many subsequent builds.
Continue reading →Digital Digressions by Stuart Sierra
From programming to everything else
Everyone likes to complain when a build tool “downloads the internet” the first time they check out a new project. But the cost is typically amortized over many subsequent builds.
Continue reading →Tell me if this story sounds familiar. At your company, there is The Tool. Everyone is required to use The Tool. It is the central information hub for the entire company. Or at least it was supposed to be. In practice, it is where information goes to die.
Continue reading →After installing the latest *env utility, I decided to stop and count how many of these things have accumulated in my shell.
Continue reading →Inspired by a recent article comparing the number of system calls at start made by various compilers, I decided to do the same with my Clojure start-time experiments.
Continue reading →I’ve heard the phrase “where information / knowledge goes to die“ applied to a variety of targets: email, wikis, various software products, even governments. But I wasn’t sure where it originated.
Continue reading →On the impossibility of separating content from presentation
I like writing in Emacs’ Org mode, not because it’s an especially good means of writing prose, but because I already use Org so heavily for notes and source code. My last post was written in Org mode. But my blog remains, as it always has been, WordPress.
Continue reading →From 2011 to 2015, I wrote an annual Clojure Year in Review post, attempting to summarize all the interesting things that happened in Clojure in the last year. After 2015, I gave up. There was just too much happening, and I couldn’t keep track of it all.
A couple of years ago, I got tired of the “Clojure start-up is slow” meme so I decided to measure it. I found that, yes, Clojure does take a measurable amount of time to boot, but the actual start time is dominated by tooling and libraries.
Since then, new ways of running Clojure have been popping up all over the net. I decided to repeat the experiment with all the ones I could find. Think of this as the “Clojure Runtime Platforms Year in Review” for 2019.
In case you didn’t know, I started a podcast this year: No Manifestos.
One of the interesting things about podcasting is that it’s difficult to know who’s listening. This has even been suggested as the reason for the genre’s success, as it prevents the aggressive tracking and reductionist analytics that have made such a cesspool of the rest of the web.
But occasionally I am curious. At the least, I want to know, roughly, how many people are listening. How can I find out?
Continue reading →The inimitable Chouser has written an exhaustive analysis of the many ways to flatten a sequence of sequences in Clojure.
Continue reading →Continuing my series of Clojure do’s and don’ts — which, as always, is a mix of technical recommendations and my personal stylistic preferences — and continuing on the topic of the previous post in this series, here are some more arbitrary rules about anonymous functions.
Continue reading →