148
Should I switch to Wayland?
(lemmy.ml)
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 01 Sep 2023
148 points (92.5% liked)
Linux
48335 readers
537 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
The biggest Sin by far of Wayland is making users think about the graphics stack. Does this feature or this app support Wayland or X? Does this Compositor support this GPU? Does this particular environment support this mixture of displays with this DPI? Do I need to set a particular env variable or change a setting to force this app to start in Wayland mode because under X11 its scaled funky. What works in each environment? What doesn't work between environments?
Well before you reach the end of this flow chart you have lost virtually all of your users. This transition has single-handedly set the Linux desktop back by 20 years in terms of supporting more users whose level of interest in configuration is limited to clicking a control next to their monitor and making things bigger or smaller.
A saner design would have handled scaling correctly from the start and would have had a permissive mode which just made everything from the users perspective work while progressively adding a correct UI to provide features like global hotkeys, screen sharing, only to those apps users had authorized like android. If it wasn't a such a clusterfuck to use it would have had orders of magnitude more users much earlier in the development phase and perhaps attracted more development interest as well.
Nobody's requiring you to use Wayland currently, I mean realistically name a Wayland-only app (excluding the ones like remote desktop apps that are replacing X11 apps that don't work at all on Wayland), they don't exist. But with new technologies will always be growing pains, the X11 -> Wayland transition will still be another few years I imagine, I mean at this point we're really only waiting on NVIDIA 🫠. It's a painful process, but one that is only so painful because it's been put off for so long, if we put it off for any longer it would've just been even worse.
It's painful because the developers took 14 years to produce something semi usable while ignoring incredibly common use cases and features for approximately the first 10 -12 years of development
Well, such is the downfall of OSS, I mean look at VR on Linux, Mesa straight up will hard crash if you try to run SteamVR on the latest versions, and the time it takes for VR related bugs in Mesa to get patched are insanely long.
Just gotta make a hubub about it until someone with the knowhow can fix it.
Nobody's requiring it until devs start not supporting X11 anymore and start saying things like "won't fix, use Wayland". Which is already happening
See: GNOME's response to a critical GTK4 bug on x11 that makes any program using GTK4 unusable on certain devices under x11
I think that's a little bit premature for GNOME to do, though I have to ask, what "certain devices" are we talking about?
certain hardware configurations. I have two computers on linux. One of them has issues with GTK4, the other one doesn't. The only difference between these machines is hardware.
And yeah, I agree that's premature for them to do
Right, what are the "certain hardware" configurations? Are they really old? Are they really niche?
if I knew what exactly was causing it hardware wise I would have a way to fix it, and I don't
given GNOME's solution is "use Wayland" (which I can't for a variety of reasons) I don't think I can ever figure out what the problem is. Their attitude from the start is already non helpful.
all I know is my hardware isn't niche nor really really old. And Im not the only one experiencing this