Today it'd perhaps be even easier to do. Both X and Wayland protocols are extensible and so adding a way of uploading extensions is simple enough. You'd run int

Today it'd perhaps be even easier to do. Both X and Wayland protocols are extensible and so adding a way of uploading extensions is simple enough. You'd run into "political" roadblocks, perhaps if you try to standardise it, but someone could just do it. A web assembly profile that provides a way of exchanging messages to allow you to build classes could easily be made to optionally either run over the network (maybe mostly for dev/debugging) or internally within an Xserver or Wayland compositor. I think the biggest challenge today is that people would be more likely to just use a web browser for most of those things that would benefit most from working over the network, and latency for locally run software isn't a big deal (my wm, which I've mentioned elsewhere, is written in Ruby and spews about a dozen lines of debug output to the terminal for every mouse move during resize and drag at the moment, and yet it's smooth enough). It'd be fun to try, though. [EDIT: One simple/fun idea as a starting point for something like that would be to simply add an extension that injects such a wasm binary as a "filter" between inbound requests and outbound events/replies]