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 fra

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.