> X's input model is complex and allows applications to spoof on input events they do not own. On the one hand, this raises serious security concerns, especially regarding mobile platforms. On the other hand, adjusting and extending X's input model is difficult and supporting features like input event batching and compression, motion event prediction together with associated power-saving strategies or flexible synchronization schemes for aligning input event delivery and rendering operations is (too) complex.
and under Why not Wayland
> The input event handling partly recreates the X semantics and is thus likely to expose similar problems to the ones we described in the introductory section.
? likely ?
This is being described like the person is not intimately familiar with Wayland but has heard that in many ways its like X so they are making assumptions and can't make a definitive statement on what does or doesn't fit their perceived needs. That seems like a bad basis for making such an important decision, maybe they should talk to the Wayland designers and see if their needs can be met (software can be changed!) before redoing all of this work, poorly.