My shoulders are pretty wide for my frame. When using most laptop keyboards and many standard keyboards, I have to tuck my shoulders in and twist my wrists. This was causing some serious pain and tension in my neck, shoulders, and wrists, likely leading toward carpal tunnel.
I made two different changes in succession that helped greatly (and I don't remember the order now):
1. With a split keyboard, the halves could be placed so my wrists are straight and my arms hold at shoulder-width, and this rapidly reduced the amount of tension I was experiencing and gradually eased my wrist issues. Tenting the keyboard and getting a vertical mouse helped as well, but I'd rate those as minor improvements, especially since I aim not to drive with the mouse as much.
2. With Colemak layout, I was able to gradually transition from QWERTY (there's a series of AHK scripts I found at the time that basically rotated triples of keys). This helped reduce wrist strain at the hand level.
Let's put it this way: the human author is capable of doing so. The LLM is not. You can cultivate the human to learn to think in this way. You can for a brief period coerce an LLM to do so.
So there's a terminology conflation issue, then: people attacking Wayland proper for issues that are actually about the 'Wayland ecosystem'. I could see that generating increasing problems if there is no observable gameplan for or encouragement to develop those pieces people have come to expect of a full desktop stack.
Mind that I have no formed opinion of Wayland myself, having not used it. Trying to deduce probable causes from hearing people duke it out here and elsewhere.
If every implementation of a protocol seems stuck with deal-breaking bugs or incompatibilities, it's time to start asking whether the protocol itself has some problems that make it impossible to implement consistently - unstated assumptions, for example, in the reference implementation that never made it to the protocol spec.
For a modern example of this in action, see Bluetooth and the madhouse of device 'quirks' you have to settle with day-to-day, since each device has subtly protocol-breaking opinions on how to implement it.
That said, this is a relatively tame tack-on to a very meaty post, not worth harping on unless the project itself has similar issues.