<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hamza Sheikh (Posts about bash)</title><link>https://www.aikchar.me/</link><description></description><atom:link href="https://www.aikchar.me/categories/bash.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 &lt;a href="mailto:@aikchar"&gt;Hamza Sheikh&lt;/a&gt; License</copyright><lastBuildDate>Tue, 17 Sep 2024 05:03:37 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Python is the New bash</title><link>https://www.aikchar.me/blog/python-is-the-new-bash.html</link><dc:creator>Hamza Sheikh</dc:creator><description>&lt;div&gt;&lt;p&gt;bash (or at least Bourne shell &lt;code class="docutils literal"&gt;sh&lt;/code&gt;) is ubiquitous in the Linux and BSD
world. Replacing it with Python will not be easy, painless, or quick. But the
plethora of base tools written in Python for Linux distributions testifies
to the mindshare Python has gained. I don't expect the likes of FreeBSD, for
example, to bring Python into &lt;em&gt;base&lt;/em&gt; anytime soon. But we as users can
certainly replace our code written in shell with Python.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.aikchar.me/blog/python-is-the-new-bash.html"&gt; Read more …&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>bash</category><category>python</category><guid>https://www.aikchar.me/blog/python-is-the-new-bash.html</guid><pubDate>Tue, 09 Jan 2018 05:03:00 GMT</pubDate></item></channel></rss>