<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Singularity on Alexey Borsky</title><link>https://volotat.github.io/tags/singularity/</link><description>Recent content in Singularity on Alexey Borsky</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://volotat.github.io/tags/singularity/index.xml" rel="self" type="application/rss+xml"/><item><title>There is No Point in Compilers, OS or Static Code Anymore.</title><link>https://volotat.github.io/p/post-von-neumann-computing/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate><guid>https://volotat.github.io/p/post-von-neumann-computing/</guid><description>&lt;img src="https://volotat.github.io/p/post-von-neumann-computing/cover.png" alt="Featured image of post There is No Point in Compilers, OS or Static Code Anymore." /&gt;&lt;p&gt;&lt;em&gt;Prefer listening? This article is also available as an &lt;a class="link" href="https://www.youtube.com/watch?v=ToPIjJda8bU" target="_blank" rel="noopener"
&gt;audio version on YouTube&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-future-is-now"&gt;The Future is Now
&lt;/h2&gt;&lt;p&gt;A bit more than a year ago, I wrote an &lt;a class="link" href="https://volotat.github.io/p/the-sunset-of-human-readable-code/" target="_blank" rel="noopener"
&gt;essay&lt;/a&gt; with my thoughts on the agentic coding wave that was only starting to gain traction back then. My main conclusion was that at some point in the future, we would have to pass our own nurturing love for programming to the AI completely. And when that happens, there will be no way back, because the machine will eventually do things that people cannot truly understand in their full capacity, as the sheer amount and complexity of code produced will simply be impractical for a human brain to comprehend.&lt;/p&gt;
&lt;p&gt;For better or worse this day has come.&lt;/p&gt;
&lt;p&gt;The best coding models assisted with the best harnesses are already better at writing clean code, debugging, researching, and keeping tons of boring routine stuff in place than most human programmers. Furthermore, they never get tired, bored, or lack pedanticity. It is not necessary to list here all the impressive things AI has achieved in recent months, as I am pretty sure anybody reading this is already well aware of it. People can simply no longer track this entire code production factory completely, and we just hope that the agent did its best most of the time.&lt;/p&gt;
&lt;p&gt;Now, this shift is starting to break all the assumptions that were put into software development over the decades. It started with the so-called SaaS-pocalypse, where almost anyone can vibe-code any service they need in an afternoon, and it leads straight to a much more fundamental question: &lt;strong&gt;why do models still have to output human-readable code if no human is ever going to read it anyway?&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="the-post-compiler-era"&gt;The Post-Compiler Era
&lt;/h2&gt;&lt;p&gt;Ever since the stored-program computer was described in 1945, the code executed on the processing unit has been a mostly static, pre-built binary stored in memory. It had to contain a massive amount of fallback cases for different types of hardware and architectures to be supported. For more than eighty years, this assumption held, largely because it was the only way to keep the ever-growing complexity of computing systems manageable by a limited human brain. We built compilers, runtime environments, and operating systems because humans could never hope to write raw, optimal machine code on the fly.&lt;/p&gt;
&lt;p&gt;I would like to argue that the code of tomorrow is never stored in memory. Some pieces of it, templates and reusable structural elements, will endure, but not all of it.&lt;/p&gt;
&lt;p&gt;Code, if you can even call it that anymore, is going to be written and executed on the fly by an AI system that exists on a dedicated neural processing unit, using the CPU and GPU as a pure processing power warehouse to calculate what is needed and produce an output for the end user. It will generate pure instructions in the native binary format, sent to the hardware in just enough quantity to make it busy enough to think about the current task and prepare the next batch of instructions, exactly in a form the processing units expect them.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://volotat.github.io/p/post-von-neumann-computing/Von_Neumann_vs_Post_Von_Neumann.png"
width="2340"
height="1162"
srcset="https://volotat.github.io/p/post-von-neumann-computing/Von_Neumann_vs_Post_Von_Neumann_hu_a1dfd11a54c61171.png 480w, https://volotat.github.io/p/post-von-neumann-computing/Von_Neumann_vs_Post_Von_Neumann_hu_456e07024b8e8945.png 1024w"
loading="lazy"
alt="The von-Neumann architecture next to the post-compiler one"
class="gallery-image"
data-flex-grow="201"
data-flex-basis="483px"
&gt;&lt;/p&gt;
&lt;h2 id="not-in-the-cloud"&gt;Not in the Cloud
&lt;/h2&gt;&lt;p&gt;When we imagine this kind of future, the immediate temptation is to picture today&amp;rsquo;s massive frontier models sitting in the cloud, writing scripts and managing our devices. But a static, cloud-tethered model is fundamentally incapable of acting as the substrate for personal computing.&lt;/p&gt;
&lt;p&gt;Every standard large language model we have today is a frozen snapshot. It was trained once at astronomical cost, cast in digital stone, and shipped with a hard cutoff date. It knows nothing about the specific machine in front of you, the timing of your memory bus, or the rhythm of what you are doing right now. Even with the local model and a powerful harness like &lt;a class="link" href="https://github.com/nousresearch/hermes-agent" target="_blank" rel="noopener"
&gt;Hermes&lt;/a&gt; that already went quite close to the adaptable personal agent, at the moment you try to fine-tune its brain - typical static LLM on your daily tasks, it forgets what it knew before. A frozen model living in a remote data center is even worse at organically adapt to your hardware or your life.&lt;/p&gt;
&lt;p&gt;This flow of reasoning was a large part of why I started experimenting with &lt;a class="link" href="https://github.com/volotat/mini-AGI" target="_blank" rel="noopener"
&gt;mini-AGI&lt;/a&gt;. I wanted to see if it was possible to build a model that doesn&amp;rsquo;t rely on tokenizers, lives on modest consumer hardware, and learns continually from a single stream of raw bytes. A model like that is not meant to be just another chatbot, but an early proof of concept for the kind of adaptable, living neural core that could actually sit on local silicon and mediate between human intent and raw hardware. It was an enormous surprise to see it actually working the first time I stated training the model in the &amp;ldquo;impossible&amp;rdquo; (as I believed it) streaming regime and seeing that it still learns without much signs of &amp;ldquo;catastrophic forgetting&amp;rdquo; visible.&lt;/p&gt;
&lt;h2 id="ephemeral-instructions"&gt;Ephemeral Instructions
&lt;/h2&gt;&lt;p&gt;In this new wave of computing, you simply do not need an operating system, a BIOS, static device drivers, or millions of lines of defensive code where ninety-nine percent of it sits completely dormant on disk.&lt;/p&gt;
&lt;p&gt;The model does not need a human engineer to write an abstract driver layer to communicate with a graphics chip or a sensor. Because it operates at the raw byte level and learns continually, it can interact with the hardware directly, learn the timing and responses of the silicon through execution feedback, and discover the most efficient instruction paths on its own.&lt;/p&gt;
&lt;p&gt;When you want to accomplish something, the system does not load an application binary from a drive. It understands your intent, synthesizes the exact machine instructions required for that specific microsecond, sends them to the execution warehouse, and the code immediately evaporates the moment the result is computed. It existed only for the brief moment it was needed, tailored perfectly to the state of the machine at that exact point in time. It is extremely efficient, and completely alien to how we have thought about software for the last eighty years.&lt;/p&gt;
&lt;h2 id="new-species"&gt;New Species
&lt;/h2&gt;&lt;p&gt;For generations, we have treated personal computers as rigid, predictable, somewhat boring appliances. You buy a box with frozen specifications, install an operating system stamped out in a corporate factory, run static programs written by strangers until you eventually replace it with better cold box, keeping only the data it had, but never the experiences it lived through.&lt;/p&gt;
&lt;p&gt;As we move toward continual, hardware-native intelligence, personal computers stop looking like boring machines and start looking much more like living, adaptable organisms that live alongside us.&lt;/p&gt;
&lt;p&gt;Instead of setting up software, you will essentially be adopting an unformed digital nervous system that maps its own hardware and begins adapting to your life. It will evolve its own internal pathways, synthesize the tools you need out of thin air, and quietly discard what it no longer uses. It will carry no corporate agenda and no frozen legacy assumptions, because its entire existence is shaped by your data and your machine. It marks the moment computing stops being a cold, static tool we operate, and becomes a genuine, living extension of our own minds.&lt;/p&gt;
&lt;p&gt;And you know what the craziest thing about all of this is?&lt;/p&gt;
&lt;p&gt;It is going to happen much sooner than we all expect. For my personal estimate, I give it just two more years until something like this actually starts appearing on the mass market.&lt;/p&gt;</description></item></channel></rss>