this post was submitted on 01 Dec 2023
136 points (97.2% liked)
Linux
48077 readers
779 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 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I am usually on the pro-Wayland side but with GNOME and KDE the Wayland implementations are fairly independent. That means that your statement that KDE going “Wayland by default is going to benefit gnome too since it’ll put more priority on bugs” is watered down somewhat.
Fixing bugs in the KDE compositor / display server ( KWin ) will not necessarily address bugs or missing functionality in GNOME ( Mutter ). A lot of what they share is also shared with Xorg ( libinput, libdrm, KMS, Mesa ).
On the application side, apps lean heavily on the toolkit libraries. KDE apps are built with Qt and GNOME apps are built with GTK. Fixing Qt bugs may not improve the quality of GTK and vice versa.
Smaller projects will share more infrastructure. Many other environments are using Wlroots as a compositor library for example. Fixing bugs there will benefit them all but again is independent of KDE and GNOME.
Your point is still valid though. For one thing, the larger the Wayland user base, the greater the number of use cases the Wayland protocol itself will be adapted to address and the more testing and development everything in the Wayland ecosystem will get.
Over time, one benefit of multiple implementations will probably be code quality. Apps that run well in multiple environments are well implemented and the same is true of environments that provide the necessarily features to a large body of apps. In that way, more bugs will be found and fixed in all environments.