The problem is that Zed has understandably and transparently abandoned supporting GPUI as an open source endeavour except to the extent contributions align with its business mission.

I remember when that came out, but I'm not sure I understand the concern. They use GPUI, so therefore they MUST keep it working and supportable, even if updating it isn't their current priority. Or are you saying they have a closed source fork now?

Actually, this story is literally them changing their renderer on linux, so they are maintaining it.

> except to the extent contributions align with its business mission

Isn't that every single open source project that is tied to a commercial entity?

I don't know what the message means exactly, but I can't plan to build on GPUI with it out there, especially when crates that don't carry that caveat are suffering from being under-resourced.

IMO, as long as Zed uses it, we are safe. If it doesn't, we aren't. I'm keeping it that simple.

They haven't. They are just heads down on other work. It wouldn't make sense for them to abandon it - they have no alternative. What that message was about was supporting _community_ prs and development of gpui.

Focus ebbs and flows at Zed, they'll be back on it before long.

I tried gpui recently and I found it to be very, very immature. Turns out even things like input components aren't in gpui, so if you want to display a dialog box with some text fields, you have to write it from scratch, including cursor, selection, clipboard etc. — Zed has all of that, but it's in their own internal crates.

Do you know how well gpui-component supports typical use cases like that? Edit boxes, buttons, scroll views, tables, checkbox/radio buttons, context menus, consistent native selection and clipboard support, etc. are table stakes for desktop apps.

Yeah, running just gpui is kinda like writing a react app without a component library. It is going to be on you to implement all your components.

All of those are handled. Run the "story" app. It is very impressive IMO.

Components list: https://longbridge.github.io/gpui-component/docs/components/

I'm not sure about that analogy: HTML provides the basic components atombender laments are missing from GPUI.

Thank you, that looks very promising indeed.

I do think gpui needs a native input element (enough that I wrote one (https://github.com/zed-industries/zed/pull/43576) just before they stopped reviewing gpui prs) but outside of that I think it is pretty ok and cool that gpui just exports the tools to make whatever components you need.

I could see more components being shipped first party if the community took over gpui, or for some crazy reason a team was funded to develop gpui full time, but developing baseline components is an immense amount of work, both to create an maintain.

Buttons (any div can be a button), clipboard, scroll views (div, list, uniform_list) should all already be in gpui.