<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Task - Tag - vo.rs</title><link>https://vo.rs/tags/task/</link><description>Task - 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>Tue, 03 Sep 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/task/" rel="self" type="application/rss+xml"/><item><title>Just and Task: Modern Alternatives to Make That Don't Make You Cry</title><link>https://vo.rs/story/just-and-task-modern-alternatives-to-make-that-dont-make-you-cry/</link><description>&lt;p&gt;Almost every project I touch accumulates a pile of little commands: build the thing, run the tests, regenerate the assets, deploy to staging. For decades the reflex answer was a &lt;code&gt;Makefile&lt;/code&gt;, and for decades a &lt;code&gt;Makefile&lt;/code&gt; has been quietly torturing everyone who isn&amp;rsquo;t compiling C. Tab-versus-space errors that print nothing useful. Recipes that fail silently because each line runs in its own shell. Variable expansion that fights you because Make has its own &lt;code&gt;$&lt;/code&gt; and the shell has another. Make is a brilliant build tool wearing a task-runner costume, and the costume doesn&amp;rsquo;t fit. This article is about two tools — &lt;code&gt;just&lt;/code&gt; and &lt;code&gt;Task&lt;/code&gt; — that fit much better.&lt;/p&gt;</description><pubDate>Tue, 03 Sep 2024 09:00:00 +0000</pubDate></item></channel></rss>