> Yes, that's a feature that some of us use. Any replacement needs to support that ability, or it isn't a functional replacement. No it doesn't. There is no ne

> Yes, that's a feature that some of us use. Any replacement needs to support that ability, or it isn't a functional replacement. No it doesn't. There is no need for any client without any permissions or privileges to be able to snoop on other processes. Why not let users decide which clients can snoop? > That's only true for a small set of X clients. What does X do? > More can be prevented if toolkits bothered to draw using X instead of re-sending client-rendered pixmaps on every update (a lot of the people complaining about X are not actually using X for most of their work). No, that is how X works. I found out this when experimenting with creating my own toolkit. The Composite extension fixes this. > Choosing to break 20+ years of software by removing these features is not an acceptable solution. It is acceptable. Most people don't use 20 year old software. XWayland can be used to keep backwards compatibility.