So you want to work remote. Or you want other people to be remote. You want space. Perspective. Distance. Escape the corporate cubicle farm and work in your pajamas.
First, you need to get some network cables.Continue reading →
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 →
After installing the latest *env utility, I decided to stop and count how many of these things have accumulated in my shell.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.