They seem to have stopped developing GPUI (or maybe just the public version)?
replyOne of the staff forked it into a community edition https://github.com/gpui-ce/gpui-ce
Does anyone have more details about the state of it?
> I wish GPUI could become the go-to Rust UI library and not just an editor backend.
replyIn case you find it useful, I recently stumbled upon this project:
https://github.com/longbridge/gpui-component
"UI components for building fantastic desktop applications using GPUI."
I took a look at gpui-component a while ago when assessing GPUI for a project I was working on. IANAL but was dissuaded because it's almost certainly not compliant with the Zed license--gpui-component "borrows" gpui code patterns lifted straight from the main zed repo, which therefore must be AGPL/GPL (unlike the gpui-only which is Apache IIRC). Caveat emptor (caveat user?).
replyI think it was even featured and praised in a recent zed blog post
replyThere's never going to be one GUI library to rule them all, but I find iced the best Rust library at the moment and likely for the foreseeable future.
replyI'm beating a dead horse here but the challenge is a11y. Chromium wrappers get a11y for free; bespoke UI frameworks must implement accesskit (or something) which is a lot of work and something that (imo sadly) many small teams decide is not worth the investment.
replyWhat's so good about GPUI?
replyI haven't used it, but it caught my attention when I read the Text Rendering section of this post:
replyhttps://zed.dev/blog/videogame#text-rendering
It looks like their approach could nicely solve a problem that's shared by almost every new GUI toolkit I've tried: text looks terrible, or at least out of place when surrounded by applications built with the desktop's native toolkit.
Clean and polished design, concise Tailwind-style API, and last but not least sustained 120 FPS across complex UI.
reply