<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Bash on Thoughts and Code</title><link>https://www.hamnis.org/tags/bash/</link><description>Recent content in Bash on Thoughts and Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 13 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.hamnis.org/tags/bash/index.xml" rel="self" type="application/rss+xml"/><item><title>Deno scripting</title><link>https://www.hamnis.org/posts/2025-deno-scripting/</link><pubDate>Thu, 13 Feb 2025 00:00:00 +0000</pubDate><guid>https://www.hamnis.org/posts/2025-deno-scripting/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Have you ever felt like you’re making too many shell scripts? Some may say that every line of &lt;code&gt;bash&lt;/code&gt; is too much &lt;code&gt;bash&lt;/code&gt;.
An example of why bash may be not the best solution for writing scripts is shellcheck. There are &lt;a href="https://gist.github.com/eggplants/9fbe03453c3f3fd03295e88def6a1324"&gt;too many possible mistakes&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In the last few years I have been experimenting with different scripting languages, and I think I have found a few good ones.&lt;/p&gt;
&lt;p&gt;A non-exhaustive list is:&lt;/p&gt;</description></item></channel></rss>