Comment by pkaeding
11 hours ago
I thought Wayland was different from X11, and didn't allow this. But I'm far from an expert on this topic so I'd like to learn more.
11 hours ago
I thought Wayland was different from X11, and didn't allow this. But I'm far from an expert on this topic so I'd like to learn more.
Wayland natively isn’t built for forwarding the way X11 is. Waypipe fixes this, providing an X11 protocol equivalent for Wayland. This project is a waypipe client for macOS.
https://github.com/neonkore/waypipe proxies Wayland over a network. It’s straightforward enough in theory: Wayland core is just a communications protocol plus shared memory; so you just need to forward the messages, and detect and send changes in the shared memory. Not the cheapest thing, but perfectly tractable. Of course, there are also more difficult extensions, like GPU integration, but that sort of thing was a problem for X as well.
This is how modern x11 worked too since nobody uses software rendering with x primitives anyway.
here is Wayland vs X11 visualised.. it might help - https://vectree.io/c/compositing-window-management-architect...
According to that page Wayland's architecture is simpler than X11.
If you put everything into a monolith, it looks simpler than if you have components that have to speak protocols to each other.
1 reply →