Migration to Hugo
After almost five years of using Pelican as my static site generator, I’ve migrated to the Hugo tool. While I enjoyed Pelican and it’s flexibility, it’s performance started to bother me when building a site from scratch. Depending on what else was running on my laptop, a full build could take 15-20 seconds. This isn’t the end of the world, but in comparison Hugo takes less than 100 milliseconds.
If it was simply a matter of build time, I may not have really cared that much, but I’ve been using Hugo to build the site and documentation for Reaper, the open source repair tool we maintain at The Last Pickle.
Lastly, over the last two years I’ve been writing less and less Python. While I’ve love the language since I started writing it, after writing a considerable amount of Rust and Kotlin over the last two years it’s become difficult to justify using a language with dynamic typing. The amount of time saved by the compiler goes up as projects get bigger, and I mostly work Reaper, Cassandra, and our own internal tooling at TLP, which is all written in Kotlin. Python’s dependency management feels a bit archaic compared to Maven and Gradle.
So here we are, with a new site generator, a new look, and hopefully some more content.If you found this post helpful, please consider sharing to your network. I'm also available to help you be successful with your distributed systems! Please reach out if you're interested in working with me, and I'll be happy to schedule a free one-hour consultation.