<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>History on cloudmato.com</title><link>https://cloudmato.com/tags/history/</link><description>Recent content in History on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Mon, 15 Jun 2026 12:21:31 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/history/index.xml" rel="self" type="application/rss+xml"/><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><item><title>How AWS Went From One Service to 200+</title><link>https://cloudmato.com/posts/aws-evolution-history/</link><pubDate>Tue, 02 Jun 2026 14:56:35 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/aws-evolution-history/</guid><description>&lt;p&gt;Amazon didn&amp;rsquo;t set out to build the world&amp;rsquo;s largest cloud platform. It stumbled into one while trying to stop its own engineers from reinventing the same infrastructure wheel every few months.&lt;/p&gt;
&lt;h2 class="header-anchor-wrapper"&gt;The Internal Mess That Started It All
&lt;a href="#the-internal-mess-that-started-it-all" 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;Around 2000, Amazon was building Merchant.com — a product to let third-party retailers like Target and Marks &amp;amp; Spencer spin up e-commerce stores on Amazon&amp;rsquo;s infrastructure [2]. What followed was an organizational disaster. Every team was independently building its own version of the same storage, compute, and database primitives. No shared APIs, no standard way to access anything.&lt;/p&gt;</description></item><item><title>History of Favicon: Why Is It Called Favicon?</title><link>https://cloudmato.com/posts/history-of-favicon-why-called-favicon/</link><pubDate>Mon, 01 Jun 2026 21:46:38 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/history-of-favicon-why-called-favicon/</guid><description>&lt;p&gt;You see it in the browser tab. You see it next to the site name in search results. You think of it as the logo of a website. So why is it called a &lt;em&gt;favicon&lt;/em&gt;? That doesn&amp;rsquo;t sound like it has anything to do with tabs or logos at all. And you&amp;rsquo;re right — it doesn&amp;rsquo;t. The name is a relic of what the icon was &lt;em&gt;originally built for&lt;/em&gt;, not what it does today.&lt;/p&gt;</description></item></channel></rss>