| ▲ | embedding-shape 5 days ago | |||||||||||||
That way you also prevent things possible in X11 to be impossible in Wayland, like a window setting it's own position, if you were to want that. | ||||||||||||||
| ▲ | accelbred 5 days ago | parent | next [-] | |||||||||||||
Good. Disallowing software to position its own windows has been a major usability improvement over the X11 days of software making stupid positioning decisions and having to patch it out everywhere... | ||||||||||||||
| ||||||||||||||
| ▲ | lotharcable 5 days ago | parent | prev [-] | |||||||||||||
Fixing X11's security would of broken window positioning as well. Since that is a security issue. The deal here is that the only way to fix X11's security issues is by breaking all those types of workflows and forcing application rewrites to implement them in authenticated ways. So if you are going have to go and break all that stuff, why not fix a crapload of other problems while you are at it? Calling Wayland "X13" may have avoided a lot of misunderstandings, but it probably would of caused others. | ||||||||||||||
| ||||||||||||||