AI Summary
5 min readScott Telinsky has been building desktop apps with a Rust-based UI framework called GPUI, and he's not going back to Electron or Tauri. On this episode of Syntax, he walks through why he made the switch, how GPUI works, and what he's built with it—including a file management tool, a window utility, and a personal dev server dashboard. The conversation is less about evangelism and more about a practical trade-off: trading web-view convenience for native performance and tiny binary sizes, at the cost of a younger ecosystem and no DOM.
Why GPUI Instead of a Web View
The core argument is about what you ship and what runs on the user's machine. Electron apps bundle a full Chromium instance, often pushing 200+ MB downloads and consuming significant RAM for even small utilities. Tauri solves the bundle size problem by using the operating system's native web view, but Telinsky found that approach limiting in practice—especially on macOS, where Safari's WebKit lacks features needed for desktop-quality apps (like hardware-accelerated canvas support or consistent CSS behavior across versions). With Tauri, you're at the mercy of whatever web view the user's OS provides, which means unpredictable feature support.
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of Syntax - Tasty Web Development Treats
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 (00:00) **GPUI as a Desktop Alternative to Electron/Tauri** - Scott introduces GPUI, a GPU-accelerated UI framework from the Zed team, and explains why he’s moved from web-view-based desktop apps to native Rust rendering.
- 2 (06:00) **What GPUI Is and How It Works** - Scott explains GPUI as a from-scratch native UI framework that renders directly to the GPU, not through the DOM or native platform widgets.
- 3 (09:36) **A Concrete GPUI Component Example** - Scott walks through a simple counter app in GPUI, showing how the code mirrors React patterns.
- 4 (11:28) **CSS Feature Coverage and Layout** - Scott assesses what CSS features GPUI supports and where it falls short.
- 5 (14:38) **Backend Logic Integration** - Scott explains how GPUI handles the separation between UI and business logic, contrasting with Electron’s RPC model.
- 6 (15:57) **Two Render Modes: Render vs. Render Once** - Scott describes GPUI’s performance optimization through two render paths.
- 7 (16:49) **GPUI Kit: The ShadCN of GPUI** - Scott introduces GPUI Kit, a component library that provides pre-built, extendable UI primitives.
+ Full timestamped outline available in the app
Show Notes
Scott and Wes ditch Electron and Tauri for GPUI, the GPU accelerated Rust UI framework from the Zed team. They get into its React-like API, styling that feels a lot like Tailwind, GPUI Kit components, the community fork drama, and the tiny desktop apps Scott has built with it.
Show Notes
- 00:00 Welcome to Syntax!
- 01:24 Electron, Tauri, and the Trouble With Web Views
- 04:05 Enter GPUI: Why We Don’t Take Money to Talk About Tools
- 05:32 Brought to you by Sentry.io
- 05:59 What GPUI Is: GPU Accelerated, Cross Platform, Native All the Way Down
- 06:50 A React Like API in Rust: Divs, Flex, and Chained Methods
- 09:35 Components, Props, and State in GPUI
- 11:21 How Much of CSS Does GPUI Actually Reimplement?
- 12:52 Flexbox Everywhere, But Where Is CSS Grid?
- 14:17 Where Does Your App Logic Live? No RPC Layer Needed
- 15:53 Render vs RenderOnce: Stateful and Static Components
- 16:57 GPUI Kit: The shadcn of GPUI
- 18:46 GPUI CE: The Community Fork and Ecosystem Tension
- 21:29 Apps Scott Built With GPUI: Gendo, File Bro, and Mr. Space
- 22:48 Why Tiny Utility Apps Should Stay Tiny
- 24:25 File Bro: File Automations a la Hazel
- 25:27 Mr. Space: Building a macOS Window Manager
- 27:05 The Downsides: No Native UI Elements and No Browser DOM
More from this podcast
Syntax - Tasty Web Development Treats →