跪拜 Guibai
← All articles
Rust

Seven Rust GUI Libraries, Two Questions: Who Draws and What Changes When Data Moves

By RockByte ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Rust's ownership rules force every GUI framework to pick an architecture for handling shared state, so the library you choose locks in your app's structure. Picking wrong means a rewrite once an app grows beyond a few screens; the article gives a checklist to avoid that.

Summary

Choosing a Rust GUI framework comes down to two questions: who draws the pixels and what happens when data changes. That's the framing here, as a developer evaluates Egui, Iced, Tauri, GPUI, Slint, Dioxus, Xilem, and GTK-rs/Relm4 for a log viewer tool. Each library picks a different answer, and those answers determine bundle size, rendering speed, and how much boilerplate you'll write.

Egui uses immediate mode: the whole UI is a function that runs every frame, reads state on the way, and releases borrows. Iced borrows Elm's architecture, with state, messages, and a single update function. Tauri hands rendering to the OS WebView and keeps Rust for heavy lifting. GPUI comes from the Zed editor and targets 120 fps with a game-like render pipeline.

Trade-offs are concrete. Egui is fast to build but looks like dev tools. Iced is structured but still pre-1.0; its last release is nearly a year old. Tauri ships small installers but depends on different web engines per OS. GPUI is built for speed but its API tracks Zed's roadmap and has thin docs. The author's own tool chooses GPUI because speed is the priority.

Takeaways
— Egui is immediate mode: the UI is a function that runs each frame, reading state and releasing borrows; it pairs with Eframe for windowing and WGPU or Glow for rendering.
— Iced is Elm-style: State, Message, Update, View; update is the only place that mutates state, and every change is a message that can be logged and replayed.
— Tauri uses the OS WebView (WebView2, WKWebView, WebKitGTK) and communicates with a Rust backend via commands; Tauri 2 stable since Oct 2024 adds iOS/Android and capabilities for scoping permissions.
— GPUI from Zed aims for 120 fps, giving each frame just over 8ms; it stores data in entities accessed via handles and renders a new element tree each frame.
— Iced 0.14.0 was released Dec 7, 2025; as of Nov 2026 it's been nearly a year without a new release, and pre-1.0 versions often require migration.
— Many Rust GUI libraries share low-level components: Winit for windows, WGPU for drawing, Taffy for layout, AccessKit for accessibility; improvements to these can benefit several frameworks at once.
— GPUI's uniform list only measures one row of equal height and draws visible rows, so scrolling a 2-million-line log can cost nearly as much as scrolling 50 lines.
Conclusions

The two-question framing (who draws pixels, what happens on data change) explains why Rust GUI libraries look so different: each is a coherent answer to the borrow checker's demands, not just a style preference.

The shared infrastructure across libraries (Winit, WGPU, Taffy, AccessKit) means the ecosystem is consolidating on lower-level components; a fix in one can lift all the frameworks built on it.

GPUI's tie to Zed is a double-edged bet: you get speed, but your API follows Zed's needs rather than the broader community's, and docs are sparse enough that you end up reading Zed's source.

Iced's near-year without a release, despite active source updates, shows that pre-1.0 Rust GUI libraries can stall in version bumps; teams should factor release cadence into adoption decisions.

Concepts & terms
Immediate mode
A UI approach where the entire interface is described from scratch every frame, typically by running a function that reads current state and emits controls; no persistent widget tree is kept.
Retained mode
Traditional GUI approach where controls persist in a widget tree and only changed parts are updated, as in GTK or Qt.
Uniform list
A list where all rows have the same height, so the layout engine measures one row and infers positions; only visible rows are rendered, making large logs cheap to scroll.
Tauri capabilities
A permission system added in Tauri 2 that limits which core and plugin commands a window or WebView can use, and scopes access for commands that support it; custom commands must be explicitly allowed.
From the discussion
Featured comments
Fritz

makePad development speed is also quite fast.

See top comments, translated →
Source: juejin.cn ↗ Google Translate ↗ Backup ↗