GPUI
GPU-accelerated Rust UI framework built by the Zed team for the Zed editor.
HN commenters like GPUI for smooth, stable, GPU-accelerated performance,123 for building cross-platform Rust desktop apps,456 and for being proven in a real product, Zed.78 Caveats include bare default components, such as a text input without IME or basic editing, that push people to write their own or use gpui-component,910 and the Zed team's warning that only Zed-relevant features get merged.11
Why people recommend it
Smooth performance · 3
Commenters describe apps built with it as smooth, stable and fast, with GPU acceleration.
“I used GPUI and the one-dark theme from Zed and it's super smooth”
“I'm amazed stable and performant it's GPUI framework is.”
Show 1 more
“So far it’s GPU accelerated (GPUI), cross platform”
Cross-platform · 3
Commenters report building apps that run on Linux, macOS and Windows.
“I'm amazed stable and performant it's GPUI framework is.”
“using native desktop APIs (gpui)”
Show 1 more
I’m vibecoding an excel in rust, for roughly the same reason in this post: what can’t be done, what are the limits. https://github.com/scosman/freecell So far it’s GPU accelerated (GPUI), cross platform, supports 95% of excel functions, supports charts, is about 40x faster than Numbers, and can render 240fps. I thought I’d leave this process with a new appreciation for manual dev/details. I haven’t found that yet. I’
Easy to build with · 3
Commenters call it amazing to build with, and one Rust developer found the code easy to understand.
“I decided to just build it using GPUI (amazing)”
“I used GPUI and the one-dark theme from Zed and it's super smooth”
Show 1 more
“GPUI is truly awesome.”
Proven by Zed · 2
It was built for a practical, non-trivial app rather than as a speculative library.
“I have not used GPUI beyond a simple test case, but had (prior to this news?) considered it for future projects.”
“I'm amazed stable and performant it's GPUI framework is.”
Rust momentum · 2
Some see it as a rising standard for Rust GUIs, even calling it React for Rust.
“GPUI is going to be react for Rust ecosystem.”
“Take a look at gpgui and glaze leading on this.”
Type-enforced hierarchy · 1
One commenter likes that its type system enforces the nesting hierarchy instead of generic nodes.
“I really do wish GPUI grew to a level where it had more users than just Zed”
Caveats and dissent
Bare components · 1
One maintainer found the default components barely interactive, including a text input without IME, a cursor or key support.
“I maintaince a video editor written in Rust and I use GPUI's fork as the GUI library.”
Zed-first development · 1
The Zed team warned that only Zed-relevant features would be merged.
“I really do wish GPUI grew to a level where it had more users than just Zed”
No accessibility · 1
One commenter notes that basic features like accessibility are missing.
“I'm amazed stable and performant it's GPUI framework is.”
Rust required · 1
Rust itself may be a barrier to entry for developers.
“I'm amazed stable and performant it's GPUI framework is.”
Possible gaps · 1
One team migrating to it is still checking what is missing and whether to contribute upstream.
“migrating Hopp's [1] overlay window, which we use for drawing the remote cursors, from winit + wgpu to gpui”
Often compared with
Who recommends it in their own words
Threads where it came up
- Show HN: I built a native app for coding agents with Rust and GPUI 2 mentions
- Cross platform Rust app that just shows Git diffs 1 mention
- Danish Government silently drops plan to dump MS Office 1 mention
- Vibecoding Photoshop: Time and pressure 1 mention
- Pi 1.0 1 mention
- GPUI Digest: Rust UI in the browser, crates distribution, release notes 1 mention
Also written as gpui. Data: gpui.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 13
“I decided to just build it using GPUI (amazing)”
“So far it’s GPU accelerated (GPUI), cross platform”
I’m vibecoding an excel in rust, for roughly the same reason in this post: what can’t be done, what are the limits. https://github.com/scosman/freecell So far it’s GPU accelerated (GPUI), cross platform, supports 95% of excel functions, supports charts, is about 40x faster than Numbers, and can render 240fps. I thought I’d leave this process with a new appreciation for manual dev/details. I haven’t found that yet. I’
“using native desktop APIs (gpui)”
“I maintaince a video editor written in Rust and I use GPUI's fork as the GUI library.”
“Take a look at gpgui and glaze leading on this.”
“GPUI is going to be react for Rust ecosystem.”
“I used GPUI and the one-dark theme from Zed and it's super smooth”
“I really do wish GPUI grew to a level where it had more users than just Zed”
“I'm amazed stable and performant it's GPUI framework is.”
“GPUI is truly awesome.”
“I have not used GPUI beyond a simple test case, but had (prior to this news?) considered it for future projects.”
“migrating Hopp's [1] overlay window, which we use for drawing the remote cursors, from winit + wgpu to gpui”