<rss version="2.0">
  <channel>
    <link>https://alexrp.com</link>
    <language>en-us</language>
    <title>Alex Rønne Petersen</title>
    <description>Alex Rønne Petersen Blog</description>
    <lastBuildDate>Thu, 06 Nov 2025 04:30:53 +0000</lastBuildDate>
    
      <item>
        <guid>https://alexrp.com/blog/collecting-isa-manuals/</guid>
        <link>https://alexrp.com/blog/collecting-isa-manuals/</link>
        <title>Collecting ISA Manuals</title>
        <description>&lt;p&gt;Going forward, I will be collecting and publishing all the manuals that I can get my hands on for various historical and contemporary instruction set architectures. The archive can be found &lt;a href=&quot;https://docs.alexrp.com&quot; target=&quot;_blank&quot;&gt;here&lt;/a&gt;, and it will be updated regularly. It’s not limited to ‘real’ ISAs; for example, I’ve included &lt;a href=&quot;https://registry.khronos.org/SPIR-V&quot; target=&quot;_blank&quot;&gt;SPIR-V&lt;/a&gt; and &lt;a href=&quot;https://webassembly.org&quot; target=&quot;_blank&quot;&gt;WebAssembly&lt;/a&gt; because they’re both major compilation targets that already have loads of compiled artifacts in the wild.&lt;/p&gt;&lt;p&gt;I hope this’ll be a useful resource for people working on compilers, assemblers, emulators, and other such tooling. It should also help combat the disappearance of ISA manuals; while building this archive, I found that far too many old or niche ISAs (10+ by my count) no longer have manuals available anywhere online! For those, short of a lucky break like someone having a local backup, the full ISA details are essentially lost to time. It’s a damn shame for that to happen in the age of the Internet. So, if you happen to have a manual that isn’t in the archive, please &lt;a href=&quot;mailto:alex@alexrp.com&quot; target=&quot;_blank&quot;&gt;email me&lt;/a&gt;!&lt;/p&gt;</description>
        <pubDate>Mon, 07 Jul 2025 00:00:00 +0000</pubDate>
      </item>
    
      <item>
        <guid>https://alexrp.com/blog/migrating-from-github-to-codeberg/</guid>
        <link>https://alexrp.com/blog/migrating-from-github-to-codeberg/</link>
        <title>Migrating from GitHub to Codeberg</title>
        <description>&lt;p&gt;I’ve decided to start the process of migrating my projects from &lt;a href=&quot;https://github.com&quot; target=&quot;_blank&quot;&gt;GitHub&lt;/a&gt; to &lt;a href=&quot;https://codeberg.org&quot; target=&quot;_blank&quot;&gt;Codeberg&lt;/a&gt;. I’ve also applied to become a &lt;a href=&quot;https://join.codeberg.org&quot; target=&quot;_blank&quot;&gt;paying Codeberg member&lt;/a&gt;, to do my part to keep the platform sustainable. I’ve already migrated my &lt;a href=&quot;https://codeberg.org/alexrp?tab=repositories&quot; target=&quot;_blank&quot;&gt;personal repositories&lt;/a&gt; and &lt;a href=&quot;https://codeberg.org/vezel&quot; target=&quot;_blank&quot;&gt;some Vezel repositories&lt;/a&gt;. I’m still working out the details for the remaining Vezel repositories, particularly in regards to CI; I’m strongly considering just renting a dedicated server and self-hosting it. I’ll still have to stick around on GitHub to work on &lt;a href=&quot;https://github.com/ziglang&quot; target=&quot;_blank&quot;&gt;Zig&lt;/a&gt; and &lt;a href=&quot;https://github.com/llvm&quot; target=&quot;_blank&quot;&gt;LLVM&lt;/a&gt; of course, but I’m moving all the repositories that I control off the platform.&lt;/p&gt;&lt;p&gt;The final straw that made me pull the trigger was &lt;a href=&quot;https://github.blog/changelog/2025-05-19-creating-issues-with-copilot-on-github-com-is-in-public-preview&quot; target=&quot;_blank&quot;&gt;GitHub’s decision to let people use AI to fill out issues&lt;/a&gt;. The signs were obviously there before, what with the Copilot buttons appearing everywhere in the GitHub UI, the &lt;a href=&quot;https://github.blog/changelog&quot; target=&quot;_blank&quot;&gt;GitHub Changelog&lt;/a&gt; being flooded with AI features, and barely any much-needed improvements or fixes being made to the core platform anymore. But now we at least have crystal clear confirmation of what GitHub is going to become over the next few years; it’s already annoying having to deal with people who dump LLM slop on issue trackers, and now GitHub wants to make that a first-class feature of the platform itself. No thanks.&lt;/p&gt;&lt;p&gt;I’m optimistic that Codeberg, being a non-profit, can avoid enshittification - which appears to be inevitable for profit-driven platforms.&lt;/p&gt;</description>
        <pubDate>Wed, 21 May 2025 00:00:00 +0000</pubDate>
      </item>
    
  </channel>
</rss>
