AI 正在推动 Rust GUI 兴趣升温
Raph Levien 认为,AI 辅助代码重写可能扩大人们对基于 Rust 的桌面和移动界面的关注,因为 Rust 兼具安全性和性能,而且据他所说,其 LLM 编程成本并不显著高于其他语言。他同时承认,Rust 仍比 TypeScript、Kotlin 或 Swift 更难编写,同时兼具 Rust 与 UI 技能的工程师也很稀缺。由于 UI 层尚无共识,他考察了 GPUI、egui、Iced 和 Xilem 等方案,并建议开发者测试性能、构建于稳固基础之上、采用明确规范,并与上游开源项目协作。
文章把 Rust 在 AI 驱动重写中的应用与尚未确定的 UI 架构选择联系起来,并指出开发者在评估性能、无障碍支持、渲染和生产就绪能力时需要权衡的因素。
Raph Levien, November 21, 2026
This is a followup to Advice for the next dozen Rust GUIs, published 4.5 years ago. The world is different in many ways, but some of the advice there is still valid. There have been roughly 20 Rust GUI toolkits announced since that blog post (see 2026 survey), but also a recent rapid acceleration of interest in Rust GUI, fueled by AI.
Rust GUI is still compelling
The motivation to build GUI apps in Rust remains strong. Many shipping GUI apps suffer from poor performance, especially when built with cross-platform technology. GUI toolkits shipped by platforms have largely stagnated, and system vendors remain uninterested in solving the cross-platform problem, so Electron has grown in popularity. RAM remains expensive and the focus is shifting to mobile, so bloat has real consequences. Building high-performance UI in Rust is a practical alternative.
Adoption of Rust UI in the past few years has been slow. Few flagship apps use Rust for their UI. One of the most notable is the Zed editor, built on their own GPUI framework. It proves that shipping Rust UI is practical, and indeed, GPUI is emerging as a major choice for AI-driven rewrites, most notably Discord. My personal sense is that GPUI is well suited to the Zed use case, and shipping in a real project boosts its visibility and credibility quite a bit, but it’s not necessarily the ideal choice for more general purpose applications. Among other things, its 2D rendering engine is well suited to a text editor, but lacks full gradient support, blending, filters, and other features expected of a renderer in the same class as Vello or Skia.