> a few distros toyed with the idea of making it the default and went back on it quickly As a bystander, it felt like a vocal minority was pretty aggressively

> a few distros toyed with the idea of making it the default and went back on it quickly As a bystander, it felt like a vocal minority was pretty aggressively underselling the shortcomings. Perhaps that's unfair but it's definitely how it came across to me. They appeared to back off a bit as a result of the community backlash, but the damage was done - many people appear to mentally associate Wayland with someone else threatening to break their system. Now we see endless threads like this one, even though Wayland itself actually seems like a really good idea to me from a technical perspective. Xorg losing maintainers is certainly a concern, but since Pipewire appears to be quickly approaching mainstream hopefully everything will work out. It's just frustrating to me that anyone ever tried to market Wayland as more than a proof of concept prior to working out such essential details (screenshots, screencasts, pointer capture, input manipulation, and a bunch of others I can't remember). I think an important takeaway is that breaking even remotely common workflows is likely to attract inordinate amounts of negative attention no matter how good your technical or circumstantial reasons are for doing so. It doesn't matter how cool the project is - most people just have no interest in hacking on their OS. > with no decent documentation in sight So it isn't just me then. I'm still using xmodmap because I never managed to figure out how to get xkb to do what I wanted.