631
Valve Engineer Mike Blumenkrantz Hoping To Accelerate Wayland Protocol Development
(www.phoronix.com)
this post was submitted on 26 Sep 2024
631 points (99.8% liked)
Linux
48674 readers
379 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
Accelerating wayland développement would mean forking it. As it is right now there's a lot of yapping in their git for every decision, small or big.
You mean feurking
what's feurking
Feurking deez nuts
An optional step in the développement process
Testing is actually mandatory, what's not mandatory though is to do it before deploying.
The authentic French translation of forking.
I'd be fine with switching over to Valve's crazy high-speed frog version of Wayland if it came down to it lol
Wayland is a protocol used by each desktop that supports it. It often moves slowly because each desktop works together and discusses each change. If valve forked it, they would just have a protocol nobody is using. If people started using it, it would just slow down again for the same reason.
If noone used it that wouldn't matter. Experimentally implemented features on a separate branch can still be useful as proof of concept to whoever is taking their time to discuss where Wayland has to go. Of course the usefulness depends on how well the Valve devs understand the needs of the desktops.
That's how you get fragmentation and instability. Then something is changed it needs to be implemented and then tested by all the desktops. If you move to fast you get ahead of development and testing which is very bad
French 🫵
The thing to keep in mind is that it is a protocol. When something is merged all downstream projects must implement it.