Rust cross-platform GPUI components

Posted by xvilka 2 days ago

Rust cross-platform GPUI components(github.com)

501 points | 210 commentspage 3

h4ch1 2 days ago|

GPUI and GPUi components are the two things I'm watching very closely while evaluating truly native GUI development.

Still waiting to see more general use before attempting to port my Svelte UI for a Tauri application but it honestly looks incredible.

Big ups to the guy(s) at Longbridge.

ape4 1 day ago||

A link to toolkit (GPUI) since I don't see it mentioned... https://www.gpui.rs/

gnarlouse 1 day ago||

So how stupid am I for asking how long it is before this is available in the browser and all the DOM behavior is WASM?

ruguo 1 day ago||

It does look pretty solid, but whenever I’m building a desktop app with Rust, Tauri is always the first thing that comes to mind.

cultofmetatron 1 day ago||

it happens to be my birthday today and this is one hell of a birthday present right now. been itching to dive into making a desktop app in rust and this looks amazing!

artursapek 1 day ago||

It seems like trading applications tend to be what demands the performance to push R&D like this for Rust GUI. My team at Kraken worked on https://iced.rs/ which powers https://www.kraken.com/desktop, a very similar application. You can definitely feel the difference in a Rust GUI vs. a web view. It can maintain high frame rates doing so much on the screen at once.

nu11ptr 1 day ago|

Are any pieces of this open source by chance? (other than iced itself)

artursapek 1 day ago||

Unfortunately not

h4x0rr 2 days ago||

Hola, finally a good rust ui framework that's not dependent on web

Ygg2 1 day ago|

You mean outside iced, slint, egui, etc. ?

phkahler 1 day ago||

Does it support app development in other languages?

UndyingHorse 2 days ago|

Why is the average binary size 10MB? Does it embed ICU data?

nicoburns 2 days ago||

I can't speak for GPUI specifically, but in general for Rust UI toolkits I'm seeing about 10-15mb for an O3 build with LTO enabled and when including things like ICU data, a WGPU-based renderer, SVG rendering support, and a "full fat" async HTTP client. More minimal builds with features disabled and/or Os/Oz can bring that down to more like 5mb.

(obviously you can also take things much higher by building more functionality into your application, but that gives you an idea of the kind of "base size" achievable).

berkes 2 days ago||

> By default, Rust optimizes for execution speed, compilation speed, and ease of debugging rather than binary size, since for the vast majority of applications this is ideal. But for situations where a developer wants to optimize for binary size instead, Rust provides mechanisms to accomplish this.

https://github.com/johnthagen/min-sized-rust?tab=readme-ov-f...

More comments...