<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Taskfile - Tag - vo.rs</title><link>https://vo.rs/tags/taskfile/</link><description>Taskfile - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sat, 28 Feb 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/taskfile/" rel="self" type="application/rss+xml"/><item><title>Taskfile: A Modern Task Runner That Replaces Make Without the Pain</title><link>https://vo.rs/story/taskfile-a-modern-task-runner-that-replaces-make-without-the-pain/</link><description>&lt;p&gt;I have a long and complicated relationship with &lt;code&gt;make&lt;/code&gt;. It is everywhere, it is reliable, and it has been quietly running the world&amp;rsquo;s builds for nearly fifty years. It also punishes you with significant whitespace, a recipe language that is really shell-inside-make-inside-shell with three layers of escaping, and the eternal indignity of &lt;code&gt;Makefile:12: *** missing separator. Stop.&lt;/code&gt; because you typed spaces where a literal tab was required. For most of what people actually use Make for these days — not building C, but running a handful of project commands — Taskfile is the replacement I wish I&amp;rsquo;d switched to years ago.&lt;/p&gt;</description><pubDate>Sat, 28 Feb 2026 09:00:00 +0000</pubDate></item></channel></rss>