upvote
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.
reply
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.
reply
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.
reply
This is how modern x11 worked too since nobody uses software rendering with x primitives anyway.
reply
here is Wayland vs X11 visualised.. it might help - https://vectree.io/c/compositing-window-management-architect...
reply
deleted
reply
According to that page Wayland's architecture is simpler than X11.
reply
If you put everything into a monolith, it looks simpler than if you have components that have to speak protocols to each other.
reply
Rio and its predecesor in Unix v8/v10 did it better than X. In some cases we got the worst:

- POSIX bloat vs Plan9's simple C and even simpler API

- ioctl's vs everything it's a file

- Complex socket spawning vs open() and dial() under Plan9/Go

- ALSA vs tuned up OSSv4, or plaing audio/mixerfs under 9front

- find -which syntax is huge- vs walk -f (or -d for dirs) | grep

- RDP/VNC/SSH/NFS/SMB vs just rcpu+auth (9p) and run rio(4) and for files... 9fs which does a simple bind()

- Symlinks and hard links vs bind and namespaces.

- GDB and SSH vs importing a remote /proc in a rio window and remote-debugging your damn remote machine as if it were your own. How cool is that? Ditto with devices. Import sound cards, network cards with the whole IP stack. NAT you say? No more.

- FFSv2 (hello OpenBSD) vs current GeFS under 9front which is like a miracle over what OBSD it's trying, the bad ZFS license or BTRFS not being ready on GNU yet. Probably the Hurd people will port GeFS to Hurd/Mach first, before BTRFS gets even ready...

- Dynamic vs static linking. 9front, a suite of multiarch compilers. Set $objtype, compile, link, deploy a standalone binary. Ready, as if it were a Go binary under Unix, but without glibc oddities. ARM binaries from 386? Done. You need a crazy long i686-gnu-foo-bar and the rest of crazyness? Not anymore. These come in src form, compile and install them, no internet required. Literal two damn commands to do so, from any to any arch.

- SH/KSH/Bash. Complexity ridden shells. Here's rc. No aliases there, just functions. No complex escaping, just () for strings, ^ to concat, ' ' for quoting. Problem solved. Even the conditonal words' syntax it's like throwing down all the complexity giving you a weirdly simple shell.

- PCRE and ex commands under vi/nvi/vim (bloat) vs Sam and structural regexes. Sam it's like a graphical vi, period, there's nothing alien of it. Imagine a modeless vi with a small frame to input commands with an easier syntax:

     x/lookup/c/replace 
These can be chained with ease.
reply