<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>History Archives - Igor Oseledko</title>
	<atom:link href="https://www.igoroseledko.com/blog-category/history/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.igoroseledko.com/blog-category/history/</link>
	<description>I know everything. Just not all at once...</description>
	<lastBuildDate>Thu, 26 Mar 2026 07:09:57 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Routing Protocols: The Internet Finds Its Own Way, Usually</title>
		<link>https://www.igoroseledko.com/blog-post/routing-protocols-the-internet-finds-its-own-way-usually/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 07:05:07 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135559</guid>

					<description><![CDATA[<p>The internet doesn&#8217;t have a map. Individual routers exchange information about reachability using protocols — RIP, OSPF, BGP — and build their own local picture of the network topology, forwarding packets based on whatever their current table says. BGP, the Border Gateway Protocol, handles routing between autonomous systems — the large networks operated by ISPs, [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/routing-protocols-the-internet-finds-its-own-way-usually/">Routing Protocols: The Internet Finds Its Own Way, Usually</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>The Turbo Pascal Miracle: A Full IDE in 64 Kilobytes</title>
		<link>https://www.igoroseledko.com/blog-post/the-turbo-pascal-miracle-a-full-ide-in-64-kilobytes/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 07:04:14 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135557</guid>

					<description><![CDATA[<p>Borland released Turbo Pascal in 1983 for $49.95 — a price that undercut the competition by a factor of ten and included an editor, a compiler, and a linker in a single executable that fit in 64 kilobytes and compiled code fast enough to feel instant on the hardware of the day. It was written [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/the-turbo-pascal-miracle-a-full-ide-in-64-kilobytes/">The Turbo Pascal Miracle: A Full IDE in 64 Kilobytes</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>COBOL: The Language Written in a Weekend That Outlived Everyone Who Wrote It</title>
		<link>https://www.igoroseledko.com/blog-post/cobol-the-language-written-in-a-weekend-that-outlived-everyone-who-wrote-it/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 07:02:56 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135555</guid>

					<description><![CDATA[<p>COBOL was designed in 1959 by a committee led by Grace Hopper, with the explicit goal of making business programming readable by non-programmers. The language used English-like syntax — MOVE TOTAL-PRICE TO INVOICE-AMOUNT — on the theory that management might actually read the source. Management did not read the source. Programmers, however, wrote enormous quantities [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/cobol-the-language-written-in-a-weekend-that-outlived-everyone-who-wrote-it/">COBOL: The Language Written in a Weekend That Outlived Everyone Who Wrote It</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Signal Handling: The Unix Asynchronous Interrupt System Nobody Gets Right First Time</title>
		<link>https://www.igoroseledko.com/blog-post/signal-handling-the-unix-asynchronous-interrupt-system-nobody-gets-right-first-time/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 07:01:53 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135554</guid>

					<description><![CDATA[<p>Unix signals are a mechanism for notifying processes of events asynchronously — SIGTERM to request termination, SIGKILL to demand it, SIGHUP historically for hangups, SIGSEGV for segfaults, SIGUSR1 and SIGUSR2 for whatever you fancy. They arrive between any two instructions, which means a signal handler can interrupt a running function at any point, including in [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/signal-handling-the-unix-asynchronous-interrupt-system-nobody-gets-right-first-time/">Signal Handling: The Unix Asynchronous Interrupt System Nobody Gets Right First Time</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>The PDP-11: The Computer That Unix Grew Up On</title>
		<link>https://www.igoroseledko.com/blog-post/the-pdp-11-the-computer-that-unix-grew-up-on/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 07:00:36 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135552</guid>

					<description><![CDATA[<p>Unix spent its formative years on the DEC PDP-11, a 16-bit minicomputer that arrived in 1970 and became the dominant research and university machine of the decade. The PDP-11&#8217;s architecture — its memory model, its instruction set, its 64KB address space limit — shaped Unix and C in ways that persisted long after the hardware [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/the-pdp-11-the-computer-that-unix-grew-up-on/">The PDP-11: The Computer That Unix Grew Up On</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Multics: The Overengineered Ancestor Unix Was Specifically Built to Escape</title>
		<link>https://www.igoroseledko.com/blog-post/multics-the-overengineered-ancestor-unix-was-specifically-built-to-escape/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 06:59:33 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135550</guid>

					<description><![CDATA[<p>Multics — Multiplexed Information and Computing Service — was a joint project of MIT, Bell Labs, and GE begun in 1964 to build a comprehensive, reliable, shared computing utility. It would support hundreds of simultaneous users, have a hierarchical filesystem, support virtual memory, be secure, fault-tolerant, and extensible. It mostly worked. It also required a [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/multics-the-overengineered-ancestor-unix-was-specifically-built-to-escape/">Multics: The Overengineered Ancestor Unix Was Specifically Built to Escape</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>The Bell System Technical Journal, 1978: The Issue That Launched a Thousand Careers</title>
		<link>https://www.igoroseledko.com/blog-post/the-bell-system-technical-journal-1978-the-issue-that-launched-a-thousand-careers/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 06:58:33 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135548</guid>

					<description><![CDATA[<p>In July–August 1978, Bell Labs dedicated an entire double issue of the Bell System Technical Journal to Unix. It contained papers on the operating system, the C language, the shell, tools, and the philosophy underlying all of them. The journal was not widely circulated outside Bell Labs and academia, but the papers that appeared in [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/the-bell-system-technical-journal-1978-the-issue-that-launched-a-thousand-careers/">The Bell System Technical Journal, 1978: The Issue That Launched a Thousand Careers</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>TCP/IP: Cerf and Kahn&#8217;s Napkin Sketch That Became the Internet&#8217;s Skeleton</title>
		<link>https://www.igoroseledko.com/blog-post/tcp-ip-cerf-and-kahns-napkin-sketch-that-became-the-internets-skeleton/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 06:57:11 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135546</guid>

					<description><![CDATA[<p>In 1973, Vint Cerf and Bob Kahn sketched out the Transmission Control Protocol in a hotel lobby, attempting to solve the problem of connecting incompatible networks without requiring any of them to change. The insight was to make the endpoints — not the network — responsible for reliability: the network would do its best to [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/tcp-ip-cerf-and-kahns-napkin-sketch-that-became-the-internets-skeleton/">TCP/IP: Cerf and Kahn&#8217;s Napkin Sketch That Became the Internet&#8217;s Skeleton</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Git: Linus Torvalds Built a Version Control System in Ten Days Out of Spite</title>
		<link>https://www.igoroseledko.com/blog-post/git-linus-torvalds-built-a-version-control-system-in-ten-days-out-of-spite/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 06:56:01 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135544</guid>

					<description><![CDATA[<p>In April 2005, BitKeeper — the proprietary version control system the Linux kernel had been using — revoked its free licence for open-source projects following a dispute. Linus Torvalds, unimpressed with the available alternatives, spent ten days writing his own. The design goals were: fast, distributed, and proof against data corruption. Git tracks content rather [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/git-linus-torvalds-built-a-version-control-system-in-ten-days-out-of-spite/">Git: Linus Torvalds Built a Version Control System in Ten Days Out of Spite</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>The Therac-25: When a Race Condition Became a Murder Weapon</title>
		<link>https://www.igoroseledko.com/blog-post/the-therac-25-when-a-race-condition-became-a-murder-weapon/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 06:54:46 +0000</pubDate>
				<guid isPermaLink="false">https://www.igoroseledko.com/?post_type=blog_post&#038;p=135542</guid>

					<description><![CDATA[<p>Between 1985 and 1987, a radiation therapy machine called the Therac-25 administered lethal radiation doses to at least six patients, killing several. The cause was a collection of software bugs in its control system — including a race condition in the user interface that, under specific timing conditions, allowed the machine to fire its electron [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/blog-post/the-therac-25-when-a-race-condition-became-a-murder-weapon/">The Therac-25: When a Race Condition Became a Murder Weapon</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
