3 ms·
X11 is inherently insecure. With Wayland, the compositor itself is privileged but all clients get access to only their frame buffers and event streams. Network
by bitwize 11y ago
X11 is inherently insecure. With Wayland, the compositor itself is privileged but all clients get access to only their frame buffers and event streams.
Network transparency is mostly irrelevant on modern desktop systems, X11 remotes modern apps poorly at best, and if you really need remote desktop access you know where to find RDP and SPICE.
The Wayland switch will be a win because X11 is almost pure cruft. The good parts are what was kept in Wayland.
- pdkl95 11y ago> X11 is inherently insecure. That depends on your perspective. Why are you accepting connections from malicious X clients? > Network transparency is mostly irrelevant on modern desktop system For you, maybe. That's an opinion that many of us do not share. > X11 is almost pure cruft It's only cruft if you limit your use cases to stuff like GTK+ that decided to only use X as a dumb framebuffer. > The good parts are what was kept in Wayland. Except for a long list of features, such network transparency, support for copying PRIMARY selections in addition to CLIPBOARD, or overriding input events of arbitrary programs. Until Wayland supports these, it isn't compatible with a lot of my tools. Just because something is "old" or has features that you personally don't mean they are "bad" features that should be removed. There are more use cases than those in you definition of "desktop".