dma_bufs can’t cross machine boundaries, so Wayland not being monolithic requires deploying another service directly onto the user’s desktop machine and having

dma_bufs can’t cross machine boundaries, so Wayland not being monolithic requires deploying another service directly onto the user’s desktop machine and having it draw everything on behalf of all the GPU-less app servers. In practice the web browser strangely takes this role, with Javascript or Wasm as both window manager and rendering API, but in this world I’m not sure why the compositor still needs to be there.