Thread 105633640 - /g/ [Archived: 989 hours ago]

Anonymous
6/18/2025, 9:16:53 PM No.105633640
Wayland_Logo.svg
Wayland_Logo.svg
md5: c1060dfa0b3b79538f836d4dc402702a๐Ÿ”
Making server side decorations an extension was a huge mistake. The one thing holding Wayland back is lack of parity with modern Xorg, and if the big desktops cannot agree on something that fundamental, among other things like tearing, why would any app developer even bother migrating away from a platform as reliable as X11?
Replies: >>105633648 >>105633668 >>105633690 >>105633693 >>105634679
Anonymous
6/18/2025, 9:18:19 PM No.105633648
>>105633640 (OP)
gnome won
Anonymous
6/18/2025, 9:20:29 PM No.105633668
>>105633640 (OP)
SSD is cancer. I hope it does a swift death.
Replies: >>105633746
Anonymous
6/18/2025, 9:22:21 PM No.105633690
>>105633640 (OP)
>server OS
>therefore they put client-server architecture into everything, even when it doesn't fit
Anonymous
6/18/2025, 9:22:42 PM No.105633693
>>105633640 (OP)
I agree. No other operating system does this and for good reason.
Anonymous
6/18/2025, 9:28:24 PM No.105633746
>>105633668
Hi, Sebastian Wick
Hope you enjoyed that ban.
Anonymous
6/18/2025, 11:08:23 PM No.105634679
>>105633640 (OP)

Wayland was completely designed for CSD so the compositor could be as 'simple' as SurfaceFlinger. Then oops fugly SSD hack. Then oops cursors are maybe suddenly server rendered not server composited https://wayland.app/protocols/cursor-shape-v1 and oops are CSD shadow or just big booty bar? https://wayland.app/protocols/kde-shadow and now came this ... https://wayland.app/protocols/ext-background-effect-v1 so now CSD first but then also maybe possibly SSD and then maybe possible decorate some parts but not others. Oh also the icon fuckery. What the clown.
Anonymous
6/19/2025, 12:05:13 AM No.105635184
theres no reason to use x11 over wayland
Anonymous
6/19/2025, 12:40:49 AM No.105635482
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).
Anonymous
6/19/2025, 12:45:07 AM No.105635520
> be me
> try to use Linux desktop in current year
> mfw Wayland is "the future" but everything is broken
>
> allegation 1: Wayland is controlled opposition
> "minimal protocol" my ass
> critical features take 5+ years to standardize
> meanwhile GNOME/KDE roll their own janky extensions
> Freedesktop moves at glacial pace, but somehow Red Hat controls everything
> remember when Canonical tried Mir?
> "community" suddenly demanded "unity" behind Wayland
> hmm.jpg
>
> allegation 2: GNOME is the new Chromium
> Red Hat pushes GNOME as "default" via Fedora/RHEL
> KDE is the "Firefox" โ€“ flexible but doomed
> GNOME forces apps to target its quirks (no client-side decorations, lmao)
> KDE tries to adopt wlroots protocols, GNOME ignores them
> 5 years later: "why does nobody support KDE anymore?"
>
> allegation 3: Steam is trapped
> Windows pushing its own store, Linux has no leverage
> SDL2 is a mess of Wayland heuristics
> XWayland is a stopgap, but long-term you must target GNOME/KDE
> GabeN sweating over Proton compatibility charts
>
> allegation 4: "Security" is a meme
> Wayland fans: "X11 is insecure!"
> meanwhile Wayland has no real GUI sandboxing
> macOS/Win32 actually isolate apps
> but hey, at least you can canโ€™t screenshot my terminal without a DE-specific hack
>
> allegation 5: Red Hat playbook
> remember PulseAudio? systemd?
> "embrace, extend, extinguish" but with extra steps
> GNOME becomes the only "officially supported" DE
> KDE devs burn out maintaining compatibility layers
> profit???
>
> tfw you just wanted to startx and vibe
Replies: >>105638283
Anonymous
6/19/2025, 4:34:29 AM No.105637059
Just sounds like FOSS needs actual software engineers, not hobbyist programmers.
Anonymous
6/19/2025, 8:34:19 AM No.105638283
>>105635520
This wall of text lets make KDE look like the good guys.
But let's not forget:
- KDE took part in the cancelling of Richard Stallman
- KDE has telemetry built in.
Replies: >>105638559
Anonymous
6/19/2025, 9:22:50 AM No.105638559
>>105638283
- KDE has virus themes that get installed with root https://www.bleepingcomputer.com/news/linux/kde-advises-extreme-caution-after-theme-wipes-linux-users-files/
- KDE devs hate XLibre and its developer https://x.com/LundukeJournal/status/1935547303739154632