154
Why Wayland adoption to have official support in programs is so slow?
(wayland.freedesktop.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Aug 2024
154 points (100.0% liked)
Linux
58697 readers
222 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
As a disclaimer: I really like Wayland and use it as my daily driver for months now with KDE/Proton.
Now my answer, based on my best knowledge:
Because there is no real Wayland to implement, the base Wayland protocols are extremely bare bone and most of the heavy lifting is done by all the different wayland compositors like hyprland, plasma, Mutter, weston, wlroots, gamescope so as a developer you don't have one target to program against (X11) but lots of different wayland implementations and those are not always doing things the same way or providing the identical interfaces/API or have the same level of features.
On my system is at least one wayland only program that works absolutely fine when started in a wlroots environment but crashes (reproduceable on different systems) with a segmentation fault in Mutter or Plasma.