<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>endianness on 🪄 Technical Sourcery</title><link>https://www.technicalsourcery.net/categories/endianness/</link><description>Recent content in endianness on 🪄 Technical Sourcery</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2018-{year} Karl Stenerud. All Rights Reserved.</copyright><lastBuildDate>Mon, 05 Jul 2021 08:02:22 +0100</lastBuildDate><atom:link href="https://www.technicalsourcery.net/categories/endianness/index.xml" rel="self" type="application/rss+xml"/><item><title>On Endianness</title><link>https://www.technicalsourcery.net/posts/on-endianness/</link><pubDate>Mon, 05 Jul 2021 08:02:22 +0100</pubDate><guid>https://www.technicalsourcery.net/posts/on-endianness/</guid><description>Byte Endianness in computers has been a constant source of conflict for decades. But is there really a clear advantage to one over the other? Let&amp;rsquo;s explore together!
Origins of the Term The terms &amp;ldquo;Little Endian&amp;rdquo; and &amp;ldquo;Big Endian&amp;rdquo; originate from Jonathan Swift&amp;rsquo;s 1726 novel &amp;ldquo;Gulliver&amp;rsquo;s Travels&amp;rdquo;. It tells of long strife culminating in a great and costly war between the empires of &amp;ldquo;Lilliput&amp;rdquo; and &amp;ldquo;Blefuscu&amp;rdquo;, because they disagreed about which end of a boiled egg to break for eating.</description></item></channel></rss>