Anonymous
8/3/2025, 1:29:11 AM
No.106121268
Wayland is shit.
0. It's kiosk trooned to desktop (so we start from a rot foundation).
1. It's async oop in C with implicit sync (ALL implementations have exploitable LPEs because of this)
2. It increases attack surface (communication is a workaround through dbus+portals+pipewire)
3. It has no security model (even xorg has one)
4. It has no protocol to ensure its "isolation" (which is simply not doing X). So it's trivial to bypass the "isolation".
5. It can suffer a DoS from moving the cursor too fast.
6. It obliterates portability among the same OS. As every compositor is comparable to a different OS.
7. Policy over mechanism.
8. The core protocols are as capable, if not less, as the curses library (reason why everyone is doing their own extensions for bare minimum capabilities).
9. Literally everyone else (windows, mac, plan9, android) has a better display server. In fact, it's hard to find such a demented attempt even among hobby OSes.
10. Mesa is adding workarounds to its code for wayland. So, not satisfied in being shit, it shit on others.
11. It's brings versioning incompatibility problem (one of the reasons for Linux to have so few ports for it) to desktop level.
12. There's no "wayland" (since the raw protocols are useless). So basically you port for kde, gnome or wlroots (a port for one, does not ensure it will work on the others. Additionally, you need to consider portals too. A port for wlroots won't necessarily work on wlroots if it were expecting a specific portal).
0. It's kiosk trooned to desktop (so we start from a rot foundation).
1. It's async oop in C with implicit sync (ALL implementations have exploitable LPEs because of this)
2. It increases attack surface (communication is a workaround through dbus+portals+pipewire)
3. It has no security model (even xorg has one)
4. It has no protocol to ensure its "isolation" (which is simply not doing X). So it's trivial to bypass the "isolation".
5. It can suffer a DoS from moving the cursor too fast.
6. It obliterates portability among the same OS. As every compositor is comparable to a different OS.
7. Policy over mechanism.
8. The core protocols are as capable, if not less, as the curses library (reason why everyone is doing their own extensions for bare minimum capabilities).
9. Literally everyone else (windows, mac, plan9, android) has a better display server. In fact, it's hard to find such a demented attempt even among hobby OSes.
10. Mesa is adding workarounds to its code for wayland. So, not satisfied in being shit, it shit on others.
11. It's brings versioning incompatibility problem (one of the reasons for Linux to have so few ports for it) to desktop level.
12. There's no "wayland" (since the raw protocols are useless). So basically you port for kde, gnome or wlroots (a port for one, does not ensure it will work on the others. Additionally, you need to consider portals too. A port for wlroots won't necessarily work on wlroots if it were expecting a specific portal).