GPUI Digest: Rust UI in the browser, crates distribution, release notes

gpui-archipelago.github.io

3 pointsVanuan2 comments

I maintaince a video editor written in Rust and I use GPUI's fork as the GUI library. For me, the biggest problem is that GPUI's components seems to have no interacts and I have to write my own components. It confuses me a lot. For example, GPUI's default text inbox has no IME support, no cusor, no Backspace or arror keys support, and EVEN CAN'T TYPE IN IT. Later I got to know gpui-component, but I had already write my own components. I'm not crirticing GPUI, but just got confused by it.

Yes, this is the first "problem" you hit when you start learning GPUI. The "capability" layer is so thin that GPUI should be treated as a framework to build frameworks, not a standalone OOTB platform like Qt or Electron. On one hand, this is good, as it provides a solid base for cross-platform tooling. But OTOH, it create conditions for extreme fragmentation that is only comparable to Web Browser wars.

So until some committee emerges to bring us "HTML5" of GPUI or Zed coughs up resources to take back GPUI reigns, the chaos will continue.

Reply on news.ycombinator.com