<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systems on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/systems/</link><description>Recent content in Systems on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 16 Jul 2026 10:00:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/systems/index.xml" rel="self" type="application/rss+xml"/><item><title>LinSight: The Hot Path Has No Async Runtime</title><link>https://www.visorcraft.com/news/2026/07/linsight-the-hot-path-has-no-async-runtime/</link><pubDate>Thu, 16 Jul 2026 10:00:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/07/linsight-the-hot-path-has-no-async-runtime/</guid><description>&lt;p&gt;The reflexive choice in modern Rust services is &lt;code&gt;#[tokio::main]&lt;/code&gt;, and the reflexive architecture is &amp;ldquo;every I/O call is async, every handler is a future, every blocking call is wrapped in &lt;code&gt;spawn_blocking&lt;/code&gt; and apologized for&amp;rdquo;; on a system monitoring daemon that polls &lt;code&gt;/proc&lt;/code&gt; and &lt;code&gt;/sys&lt;/code&gt; and pushes a number to clients over a loopback socket, every one of those reflex choices is overhead you do not need, and the result is a hot path that does the same work in roughly a ninth of the time with a tenth of the resident footprint, because the runtime was never the right tool for the job in the first place.&lt;/p&gt;</description></item></channel></rss>