<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Command-Line on cloudmato.com</title><link>https://cloudmato.com/tags/command-line/</link><description>Recent content in Command-Line on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Wed, 17 Jun 2026 18:33:01 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/command-line/index.xml" rel="self" type="application/rss+xml"/><item><title>Why PowerShell Exists When CMD Was Already There</title><link>https://cloudmato.com/posts/why-powershell-when-cmd-exists/</link><pubDate>Wed, 17 Jun 2026 18:33:01 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/why-powershell-when-cmd-exists/</guid><description>&lt;p&gt;You open Windows 11, right-click the Start menu, and you see: &lt;em&gt;Command Prompt&lt;/em&gt;, &lt;em&gt;PowerShell&lt;/em&gt;, &lt;em&gt;Windows Terminal&lt;/em&gt;. Three things. You just wanted to run a quick command. Now you&amp;rsquo;re questioning your life choices.&lt;/p&gt;
&lt;p&gt;This confusion is real, and honestly, Microsoft did not make it easy. But there&amp;rsquo;s a genuinely good reason PowerShell exists — and once you understand it, the whole picture starts to make sense.&lt;/p&gt;
&lt;h2 class="header-anchor-wrapper"&gt;CMD Was Never Really a Shell — It Was a Stopgap
&lt;a href="#cmd-was-never-really-a-shell--it-was-a-stopgap" class="header-anchor-link"&gt;
&lt;svg
xmlns="http://www.w3.org/2000/svg"
width="1rem" height="1rem" viewBox="0 0 24 24" fill="none"
stroke="currentColor" stroke-width="2" stroke-linecap="round"
stroke-linejoin="round"&gt;
&lt;line x1="4" y1="9" x2="20" y2="9"&gt;&lt;/line&gt;&lt;line x1="4" y1="15" x2="20" y2="15"&gt;&lt;/line&gt;&lt;line x1="10" y1="3" x2="8" y2="21"&gt;&lt;/line&gt;&lt;line x1="16" y1="3" x2="14" y2="21"&gt;&lt;/line&gt;
&lt;/svg&gt;
&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s start at the beginning. &lt;code&gt;cmd.exe&lt;/code&gt; — the Command Prompt — has been around since Windows NT launched in &lt;a href="https://en.wikipedia.org/wiki/Cmd.exe"&gt;December 1987&lt;/a&gt; [1]. Before that, COMMAND.COM handled things in MS-DOS. So yeah, Windows has had a command-line interface for nearly 40 years.&lt;/p&gt;</description></item><item><title>The History Behind 10 Unix Commands You Use Every Day</title><link>https://cloudmato.com/posts/top-10-unix-commands-history/</link><pubDate>Mon, 15 Jun 2026 12:21:31 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/top-10-unix-commands-history/</guid><description>&lt;p&gt;I type &lt;code&gt;ls&lt;/code&gt;, &lt;code&gt;cd&lt;/code&gt;, and &lt;code&gt;grep&lt;/code&gt; probably a few hundred times a day. Never once, in 8+ years of doing this, did I stop to wonder where these tiny two-and-three letter words actually came from. Turns out, almost every single one of them has a story — some guy at Bell Labs in the early 1970s, working on a machine slower than your smartwatch, solving a problem he had &lt;em&gt;that exact day&lt;/em&gt;. Let&amp;rsquo;s go through ten of the most-used Unix commands and dig into why they exist.&lt;/p&gt;</description></item></channel></rss>