|
|
|
|
|
by superkuh
275 days ago
|
|
As an aside, you talk about wayland as if it were one thing. But the wayland protocol is intentionally minimal. Each wayland compositor picks and chooses between different third party libs to support various features. So you never know if something will actually work on the wayland compositor you use. If you stick within your ecosystem, yes, but it's not unified like X11 linux is. It's very fragmented and one's personal experience definitely doesn't say anything about other people's experience. Unlike with X11 where everyone uses the same thing. For example, mouse and keyboard support and libei, libinput, or nothing (looking at you, weston). You never know what you're going to get and so applications that need to do basic keyboard/mouse things have to guess. It doesn't work all the time. In X11 it does. Another example, accessibility features. The only wayland compositor that supports screen reading is GNOME's. They invented two new protocols, incompatible with all existing linux accessibility libraries. Only GNOME's wayland compositor and userspace applications use them. So, in summary: one's experience can't be extrapolated with wayland because there is no single wayland. |
|