<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Development on HyperCrux.com</title>
    <link>https://hypercrux.com/tags/development/</link>
    <description>Recent content in Development on HyperCrux.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hypercrux.com/tags/development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Long a New HyperCrux Engine in C Would Take: Four to Six Weeks, Phase by Phase</title>
      <link>https://hypercrux.com/how-long-a-new-hypercrux-engine-in-c-would-take-four-to-six-weeks-phase-by-phase/</link>
      <pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://hypercrux.com/how-long-a-new-hypercrux-engine-in-c-would-take-four-to-six-weeks-phase-by-phase/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/hypercrux/hypercrux/blob/main/BETA.md&#34;&gt;Beta plan&lt;/a&gt; describes a new database engine for HyperCrux, written in C, with all four handles built in. A plan like that needs a time estimate before anyone decides whether to start it. Here it is: about 19 to 30 working days of development to reach the Beta gate, which comes to roughly four to six weeks of calendar time with a working session most days. A first working version with all four handles would come in about a week.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
