> Nobody is forced. [...] You can choose not to support Wayland in your app if you want. As market-share grows, your available reach will shrink. What is the p

> Nobody is forced. [...] You can choose not to support Wayland in your app if you want. As market-share grows, your available reach will shrink. What is the point of claiming "no one is forcing you to choose X" while at the same claiming "but if you choose Y you will face the consequences"? In this case the consequence is a million frustrated users not being able to say, take a screenshot, spamming my inbox like crazy, me abandoning Linux desktop development and everyone getting frustrated at the state of the Linux desktop yet again. > There's good reasons Wayland is being adopted in major distros - and it's not "the shiny" like you asserted. Even in your own messages you are throwing the argument that "at least Wayland is maintained and Xorg isn't", which is basically another way of saying that it has developer interest, and my claim is that it has developer interest because it's new. > Your game won't even exist in 20 years The software I am talking about is actually already older than that. > Nor do you have to even care about what protocol/compositor/lib is being used unless you're doing something strange As mentioned in TFA, there are several extremely common usecases which are broken by these changes. Certainly Wayland is just part of the problem, as it is pervasive to this world.