Vanuan

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.

I believe it's never been a better time for cross-platform desktop GUI. Vulkan API works on Windows, Android, Linux. Even web has Vulkan support. The only outlier is Apple.

On Linux, Wayland provides better drawing surface and input API.

The only missing piece is a high-level GUI and Vulkan/Metal compatibility layer. Along with ancient issue of packaging of course.

Didn't they also invent Electron for their Atom editor when working at GitHub? Which then was hijacked by Microsoft and VS Code. Was Electron (Atom Shell) a core differentiator of Atom? Absolutely. Was it a business decision? No, it was a dream to use javascript/html/css to build a desktop editor. I think, similarly, Zed was an experiment to build a modern desktop app without any C++ legacy or OS API wrappers.