And yet, for all the gnashing of teeth, those people never seem to appear. Fixing X11 is basically shaving an infinite number of yaks. Wayland is the X11 deve

And yet, for all the gnashing of teeth, those people never seem to appear. Fixing X11 is basically shaving an infinite number of yaks. Wayland is the X11 developers trying to bound the problem to a finite number of yaks. They can only do this by punting everything they possibly can out of the system. To be perfectly honest, the Wayland developers don't have an option. Screenshots are a continual complaint--but it is by no means settled as to what entity and mechanism controls the security and permissions behind that and how. Punting window decorations to the clients is annoying--but any other choice likely means that you need a full text rendering system in your window manager. And if you want an "interesting" task, go help both the X11 and Wayland devlopers deal with all the race conditions and problems around the "simple" task of integrating with Vulkan and getting/presenting a surface and handling the swapchains (extension VK_KHR_surface, VK_KHR_swapchain, VK_KHR_xlib_surface, VK_KHR_wayland_surface)--lots of bugs exist and have since 2015. Try tackling the sequence of events around "resize"--you're in for an eye-opening experience. Yet, even after the Wayland guys atomized this stuff, nobody in the open source software world is picking up the work. Maybe the DeadRat guys are rejecting submissions, but I suspect it's more that people simply aren't willing to grind through this stuff. It's a bunch of detailed, system-level programming with LOTS of gotchas all over the place. Dunno. Maybe they should say that they are rewriting it in Rust. That might actually attract some people willing to put in work.