Port Gram to WGPUI (GPUI / WGPU rewrite) or move to separate project? #76

RandomScientist commented 2026年03月10日 01:01:38 +01:00

If the goal of gram is to focus on stability it seems reasonable to work to reduce and eventually eliminate the monorepo coupling between gram's GPUI and gram itself. This would provide a great starting point for a community-focused fork of GPUI, following gram's principles but intended for general use.

If the goal of gram is to focus on stability it seems reasonable to work to reduce and eventually eliminate the monorepo coupling between gram's GPUI and gram itself. This would provide a great starting point for a community-focused fork of GPUI, following gram's principles but intended for general use.

RandomScientist commented 2026年03月10日 01:10:34 +01:00

Another thought i just had is that if we "beat" Zed to improving gpui for general use both gram and gram gpui stand to benefit from projects choosing to be downstream of us rather than zed

Another thought i just had is that if we "beat" Zed to improving gpui for general use both gram and gram gpui stand to benefit from projects choosing to be downstream of us rather than zed

krig commented 2026年03月10日 06:48:18 +01:00

Yes! I really like this idea. Split it out, switch to WGPU and stabilize.

We’ll need to rename it. But yeah, sounds great to me.

I would also like to move the UI component library out so other tools can use it more easily.

Yes! I really like this idea. Split it out, switch to WGPU and stabilize. We’ll need to rename it. But yeah, sounds great to me. I would also like to move the UI component library out so other tools can use it more easily.

juliancoffee commented 2026年03月11日 14:35:20 +01:00

There are already forks of GPUI; maybe use them or reach out to them?

https://github.com/Far-Beyond-Pulsar/WGPUI

And maybe some others ^^'
There's also an official one by the Zed team, but it's kinda dead
https://github.com/gpui-ce/gpui-ce

And, this, but might be ... a bit new?
https://github.com/ahkohd/ggpui

That one is probably the most stable https://github.com/Far-Beyond-Pulsar/WGPUI

There are already forks of GPUI; maybe use them or reach out to them? https://github.com/Far-Beyond-Pulsar/WGPUI And maybe some others ^^' There's also an official one by the Zed team, but it's kinda dead https://github.com/gpui-ce/gpui-ce And, this, but might be ... a bit new? https://github.com/ahkohd/ggpui That one is probably the most stable https://github.com/Far-Beyond-Pulsar/WGPUI

krig commented 2026年03月11日 15:28:29 +01:00

If we could move to WGPUI that would be great, would solve the WGPU transition as well.

If we could move to WGPUI that would be great, would solve the WGPU transition as well.

fzzr commented 2026年03月13日 17:39:51 +01:00

Also, take a look at Lapce's UI-lib floem.

Also, take a look at [Lapce](https://lap.dev/lapce/)'s UI-lib [floem](https://github.com/lapce/floem).

ItsHarper commented 2026年03月19日 04:53:36 +01:00

Worth noting that a PR to switch to wgpu without switching to an external fork of gpui has been merged.

Worth noting that a PR to switch to wgpu without switching to an external fork of gpui has been merged.

krig commented 2026年03月19日 07:50:56 +01:00

@ItsHarper wrote in #76 (comment):

Worth noting that a PR to switch to wgpu without switching to an external fork of gpui has been merged.

I am still thinking that the best solution long term would be to switch to an external fork if possible, and I would want to contribute any fixes or discoveries in the WGPU move there if/when doing the switch.

@ItsHarper wrote in https://codeberg.org/GramEditor/gram/issues/76#issuecomment-11806386: > Worth noting that a PR to switch to wgpu without switching to an external fork of gpui has been merged. I am still thinking that the best solution long term would be to switch to an external fork if possible, and I would want to contribute any fixes or discoveries in the WGPU move there if/when doing the switch.