<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Slint on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/slint/</link><description>Recent content in Slint on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 22 Oct 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/slint/index.xml" rel="self" type="application/rss+xml"/><item><title>State Boundaries in Rust GUIs: egui vs. Slint</title><link>https://drlongnecker.com/blog/2026/10/slint-vs-egui-rust-desktop-state-management/</link><pubDate>Thu, 22 Oct 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/10/slint-vs-egui-rust-desktop-state-management/</guid><description>&lt;p&gt;As Rust continues to be the platform of choice for quick and easy Windows and Linux development, I&amp;rsquo;ve stood up several Rust desktop applications this past year as I migrate tooling away from heavy C++ legacy apps and light (but fragile) PowerShell scripts.&lt;/p&gt;
&lt;p&gt;Architecturally the apps couldn&amp;rsquo;t be more different.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;an internal data inspection tool built with egui, full of dense panels, diagnostic tables, and deep tree views.&lt;/li&gt;
&lt;li&gt;a monitor dock built with egui for various upstream token usage (it&amp;rsquo;s a rite of passage these days, right?).&lt;/li&gt;
&lt;li&gt;a power management and profiling tool built with egui with millisecond-based charting, rapid data storage, and deep Windows telemetry integration.&lt;/li&gt;
&lt;li&gt;an internal service-management daemon and dashboard built with Slint, featuring process lifecycles, live log streaming, remote telemetry, and confirm dialogs for high-risk system operations.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;As you can see, most of my experience has been with egui as that had a natural transition from C++, but, so far, I like Slint too. The declarative syntax reads cleanly, the layout engine is predictable, and compile-time UI checking catches errors before runtime. However, state management in the dashboard began to feel surprisingly heavy. Changes that should have taken two lines of code required twenty lines of synchronization glue, and I found myself staring at roughly 200 &lt;code&gt;.clone()&lt;/code&gt; calls scattered across the application.&lt;/p&gt;</description></item></channel></rss>