<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Cli - Tag - vo.rs</title><link>https://vo.rs/tags/cli/</link><description>Cli - 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, 13 Feb 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/cli/" rel="self" type="application/rss+xml"/><item><title>Writing CLI Tools in Go: From Zero to Useful in an Afternoon</title><link>https://vo.rs/story/writing-cli-tools-in-go-from-zero-to-useful-in-an-afternoon/</link><description>&lt;p&gt;I write a lot of little command-line tools. Glue that wires two APIs together, a thing that munges a CSV the way I actually need it, a daemon that watches a directory and pokes something when a file lands. For years my reflex was a Bash script that grew tentacles, or a Python file that worked fine on my machine and nowhere else. These days I reach for Go, and I keep reaching for it because the gap between &amp;ldquo;idea&amp;rdquo; and &amp;ldquo;a binary I can hand to someone&amp;rdquo; is genuinely about an afternoon. Here&amp;rsquo;s why, and how.&lt;/p&gt;</description><pubDate>Tue, 13 Feb 2024 09:00:00 +0000</pubDate></item></channel></rss>