Link to article: https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277?permalink_comment_id=4749746
This OUTDATED article gets posted all the time. The full story is the guy is a massive FreeBSD fan so he is trying to convince more people to keep on using Xorg because he wants to make sure it isn’t abandoned. Reason for that being that Wayland is built with Linux in mind and would not work under FreeBSD without a lot of effort bwing put in as it uses some Linux-specific components or libraries.
Let’s go through the article point by point:
Wayland is broken by design:
-
A crash in the window manager takes down all running applications: Yes, because the compositor IS the server, window manager AND compositor at the same time.
-
You cannot do a lot of things: What, like allowing Windows to see your keystrokes, which makes developing a keylogger absolutely trivial?
-
There is not /usr/bin/wayland: Yes, because Wayland is a set of protocols, which a bunch of projects can implement as few or as many of, as they see fit, thus avoiding the issue of “unmaintainable mess” that has plagued Xorg for years.
-
It offloads work to the window manager: Again, yes, that’s a part of its structure: do the protocols, then let the compositor implement them. That way, you have multiple implementations running simultaneously that are well integrated with their window managers and thus more efficient and performant. It also means that when a compositor suffers from too much cruft, we can just make a new one, while application developers wouldn’t really have anything to change because if their application works on Wayland, then it works on different compositors (unless it is made specifically for GNOME, or specifically for wlroots, like wlr-randr)
…so what works on DE 1, doesn’t necessarily work on DE 2: True, because oftentimes, it doesn’t need to. Not implementing features can lead to a more lean and streamlined software solution. However, sometimes features are necessary and only implemented in some compositors. This usually happens because the universal solution is not ready. KDE are often known to do this with Plasma and KWin.
- Wayland breaks screen recording applications: Correction: The following screen recording applications were not built to support Wayland (because Wayland is new to them or they just decided not to, or they were either too busy or too irresponsible enough to realise Wayland is coming, and has been for over 10 years. In defence of the devs, they probably wanted to make sure Wayland will become stable enough, but it has been the default even on Debian for many years now, so…
In terms of the applications, I’m not aware of many of them, and for this sort of application, I’m sire alot of work is required to change the graphical backend, so I understood that some smaller projects gave up, but OBS has been working on Wayland for quite a while. Is it perfect? I don’t think so, but back when Brodie Robertson was using Hyprland, he was recording his videos using OBS. This article is quite outdated.
- Wayland breaks screen sharing applications:
As the update shows, Jitsi now does work on Wayland.
Zoom only seemed to work on gnome, BUT if you open up the Link to the zoom issue and read through the comments, there is clearly a person that clearly states that they changed /etc/os-release from PureOS to debian and it worked for them, all because of some pointless limitations enforced by the Zoom developers. As the person posting the issue states “Currently, the zoom application has put an arbirtrary restriction on screensharing so it ONLY works on GNOME, when the api being used works on all wayland desktops.” Read that again. It’s a pointless restriction put there by the Zoom team because they couldn’t be bothered to test anything non-GNOME.
And the last issue is a problem with the article writer’s own appimage. I don’t know about that one.
- Wayland breaks automation software
As stated IN YOUR FACE, it is an application that works on X11 only. Yes, Wayland is not made to use such applications, but it doesn’t mean they can’t exist. Every heard of ydotool (remember that name)? Now you have.
Next up, we have 3 issues about GNOME and KDE global menus (1 for GNOME, 2 for KDE). From the little I know about global menus and using these projects, as well as considering that they are both incredibly stable on Wayland and Fedora KDE will be dropping Xorg completely, I think it’s safe to assume these issues have probably been fixed. Please correct me if I’m wrong.
-
Wayland breaks AppImages that don’t ship a special QT plugin: Great! Just ship the plugins then! Problem solved! Also, quote from the article: “However, there is a workaround: “AppImages which ship just the XCB plugin will automatically fallback to running in xwayland mode” (see below).”
-
Wayland breaks Redshift: Once again, a program built for Xorg doesn’t always work on Wayland. Especially if it works with the compositor, like a colour temperature control application, or a wallpaper setter. The article quotes that “Redshift does not support Wayland since it offers no way to adjust the color temperature” which is not true, as proven by Redshift alternatives like Gammastep.
-
Wayland breaks global hotkeys: I present to you: Hyprland (where you can get global hotkeys). Now, it is normally not allowed by design, as a security measure, but Hyprland has not allowed that to stop them from implementing a solution where you can choose keys that will be passed on to the application. Boom, problem solved. Unfortunately, it doesn’t seem to be implemented anywhere else, as far as I know.
-
Wayland does not work for XFCE: Come back to me in late 2024 after XFCE 4.20, which will introduce Wayland support, has been released. Also, https://wiki.xfce.org/releng/wayland_roadmap
-
Wayland does not work properly on Nvidia Hardware: It keeps on getting closer but is not there yet, or so I’ve heard. Apparently, the issue is with the proprietary drivers, as noveau works well. But I use AMD, so I’m only working off rumours and opinions here.
-
Wayland does not work properly on Intel hardware: Again, I’m using AMD, so I can’t confirm or deny this, but considering the Intel drivers are open source, and I’ve heard about many, many improvements made on the Intel side of things, I think it would be reasonable to assume it has been fixed.
Edit: As multiple Intel users have pointed out in the comments, there seem to be no issues on Wayland with Intel hardware.
-
Wayland prevents GUI applications from running as root: This one has been crossed out as the article writer admits there is a solution
-
Wayland is biased towards Linux and breaks BSD: Arguments seem valid, and I’m guessing, are correct. This one is likely true and will remain so for the foreseeable future.
Edit: And yet, it seems that there are Wayland compositors for FreeBSD, so the above might only be true for OpenBSD and others.
-
Wayland complicates server side decorations: From what I’ve heard, this is true, mainly something to do with some GNOME agenda, as the article states. I think that one is true.
-
Wayland breaks windows raising/activating themselves: The linked issue is closed and seems to be resolved. There is a mention of a WIP protocol at the time (2019) that woukd fix this. I had difficulty following the discussion, but I think this has been fixed.
-
Wayland breaks RescueTime: Because RescueTime depends on X11-only tools like xprop.
-
Wayland breaks window manager: What you’re describing is Wayland breaking X11-only tools for doing various tasks in a window manager. They are X11 tools, so of course they don’t work on Wayland. I’m not sure if there are alternatives, but I’d guess there probably are. I know for a fact that Xrandr has alternatives like wlr-randr and kanshi for wlroots.
-
Wayland requires {instert WM here} to implement Xorg-like functionality:Yes, it does.
Quote from article: "As it currently stands minor WMs and DEs do not even intend to support Wayland given the sheer complexity of writing all the code required to support the above features. "
DEs: GNOME, KDE, MATE, XFCE, Cinnamon, Budgie, Enlightenment, and recently even Pantheon have either announced to start work on, have started work on, or already support Wayland.
Window managers: Qtile is doing it. Xmonad wants to hire a dev to do it. Dwm has a spiritual successor called dwl. i3 has a drop-in replacement called sway. Openbox has 2 spiritual successors called labwc and waybox. Now you might notice one of the biggest WMs is missing on here: AwesomeWM, which is such a shame. The Awesome devs have said they would be okay with someone taking on that challenge (which has already been attempted, as evidenced by the existence of way-cooler), but it seems that they wouldn’t do it themselves.
As for the projects mentioned in the article, (JWM, TWM, XDM, IceWM) they are too small and obscure, and will likely fade away with Xorg.
-
Wayland breaks _NET_WM_STATE_SKIP_TASKBAR protocol I don’t know about that one, ao I’ll assume it is still the case. Edit: Ignoring the fact that the link is broken, it basically just links to a docs change where skipTaskbar is marked as unsupported on Linux. Link: https://github.com/electron/electron/pull/33226
-
Wayland breaks NoMachine NX The link points to a page that has this marked as “SOLVED, Released in version 8” so I’m guessing it has been solved.
-
Wayland breaks Xclip: As you said it yourself, Xclip is an X11 application, so it doesn’t work on Wayland. Of course it wouldn’t work on Wayland. With Wayland, we’re trying to prevent what happened with Xorg from happening again, or am I wrong?
Edit: As pointed out by some people in the comments, there are also alternatives to xclip like wl-clipboard.
-
Wayland breaks SUDO_ASKPASS: That link seems to point to the way this issue has been resolved so I don’t see your point.
-
Wayland breaks X11 atoms: I lack knowledge on the topic so will assume this to be a valid argument
-
Wayland break games: I’m 99% sure you can disable Vsync??? But I’m not a gamer. Also, WINE on Wayland is getting better and better. Soon enough, I hope the subpar performance will become better performance (when compared to Xorg)
-
Wayland breaks xdotool: Well, yes. There is ydotool, but you’re looking for a 1-to-1 replacement and I’m not sure if ydotool fits the bill for that.
-
Wayland breaks xkill: Well, yes. Again. It is an X application, so of course it does. Though for some reason I remember it working once on wayland. Must have been an xwayland app, or maybe I’m just misremembering this.
-
Wayland breaks screensavers: Yeah, that seems to be the case.
-
Wayland breaks setting the window position: That is a WIP for Plasma, not sure about any other projects, so assume true for anything else.
-
Wayland breaks color management: Not anymore. That is being actively worked on.
-
Wayland breaks DRM leasing: While not rhat familiar with the issue, my understanding of the topic is the article is correct: not all compositors support it.
-
Wayland breaks in-home streaming: Not familiar with this, so will assume true.
-
Wayland breaks NetWM/EWMH: Yeah, that seems to be the case.
-
Wayland breaks window icons: Yeah, that seems to be the case, as said in the article, when no .desktop files are used.
And that concludes my response to this article based on my fairly limited knowledge on the topic. If I got anything wrong, please, please let me know. As you can see my knowledge is quite limited, and as such, any corrections (preferably backed up with evidence) would be appreciated
What a stupid article. It’s like saying “stop using electric vehicles because you can’t use gas stations”. I don’t understand why he’s so adamant about this? It’s not like Wayland had about 20 years of extra time to develop like X11. People keep working on it, and it takes time to polish things.
As someone with 0 investment in this whole ecosystem, I saw and perused this article like a week ago, and my immediate impression was “Why is this guy constantly saying ‘Wayland breaks XXXXX’? Wayland isn’t breaking anything, it’s new tech. Wayland has certain features, or it doesn’t or doesn’t yet. The only folks breaking anything are those swapping use of X with Wayland, within various apps or tech stacks, potentially prematurely, where Wayland doesn’t yet have the full set of features needed.”
Whoever this is seems to have a really poor understanding of long-term software development, despite being way more invested in it than I am.
Wow, I couldn’t have put this better myself. This is basically the short and simple versions of most of these arguments.
It feels like “English is broken because my friend only knows German.” to me. English works just fine. Teach your friend English.
English is Wayland. German is X11. Friend is software.
You forgot the part where they don’t need Wayland and its reduced features, because everything works fine in Xorg.
Stop pushing people towards Wayland, let it happen naturally when it will be ready and better, and they’ll come. Trying to force adoption will just make people resent it.
because everything works fine in Xorg.
… for you. I got the honor to try to find the correct match of specific NVIDIA driver version, desktop environment and compositor to get anything even remotely usable back when NVIDIA only supported Xorg. I was greeted with either an entire crash, black screen, graphical glitches, and/or screen flickering if I forgot to pin package versions. Connecting displays from right to left crashed everything, so I was forced to change my display setup to left to right. Of course, waking up displays from sleep never worked either. So don’t pretend that Wayland is a broken mess while abandonware Xorg is our Lord and savior.
Stop pushing people towards Wayland, let it happen naturally when it will be ready and better, and they’ll come. Trying to force adoption will just make people resent it.
Software vendors drag their feet to adopt Wayland as nobody forces them to adopt Wayland. Again, Wayland works fine. X11 features don’t work in Wayland. But Wayland isn’t X11. Xwayland solves a lot of these problems. Software vendors back then didn’t port their Windows software to OS/2 due to OS/2’s Windows compatibility. Video game publishers today don’t port their games to Linux in part due to Steam Proton. Software vendors today don’t port their X11 software to Wayland due to Xwayland. So the ideal solution is to force a critical mass to adopt Wayland, drop Xwayland, and let software vendors suffer from the consequences of ignoring 16 years of Linux desktop protocol innovation.
I’m glad Wayland solves problems for you, but it creates them for others.
Imagine being forced to go the other way. Could you be coerced into going back to Xorg? What would you do if a distro attempted to do that to you?
You forgot the part where this is what is happening.
The Linux ecosystem is not the product of a giant corporation. It is highly distributed and both built and promoted by multiple players with many different goals and interests.
The people actually building the ecosystem have aligned almost completely on Wayland. The strong implication is that X was not working for them.
Distributions have been slower to move but that is happening now. You can look at this as forcing users to move. My guess is that it is more a case of pleasing some uses and frustrating others where more users want what Wayland provides than miss what it doesn’t.
It is always painful to be a laggard during a technology transition. There is usually a period where the new tech becomes common before it does what you want. That is just what technology transitions look like. When that happens, the problem is that the majority is perfectly happy and maybe happier than ever. That is why things happen when they do.
You forgot the part where this is what is happening.
All I see is a rift in the community over one side pushing software that’s beta-quality at best, and acting very arrogant and dismissive towards real adoption impediments.
Which is par for the course for Linux, naturally, but “it’s happening” is wishful thinking at this stage. At this rate and with this attitude it will take at least another 5 years.
Wayland’s worst enemy is its own fans.
As I like to stay evidence driven, I should say that I use XFCE mostly and, as such, am not typically a Wayland user on most of my machines. I will let other readers decide how that impacts the indictment “Wayland’s worst enemy is its fans”.
I am not sure what the “sides” are here either. If I was to try to draw that line, it seems to be between people providing software and those using it. Because the people writing the software are moving to Wayland.
Which leads us to “at this rate”. GNOME and KDE will both be Wayland only next year. What percentage of the Linux Desktop population do we think that represents right there? Enlightenment has already moved. Ubuntu uses Wayland. Red Hat uses Wayland. The Steam Deck uses Wayland. XFCE and Cinnamon will move next year. Wayland only window managers are appearing and gaining in popularity. What percentage of the Linux Desktop universe are you expecting will still be using X at the end of 2025?
Some people may wait 5 years. Then again, Ref Hat will have stopped contribute to X by then and, as I said, nobody is rushing in to dev X. How long is running X going to stay viable?
I would say that BSD may take a little longer but they are starting to move too.
Liking Wayland or not has nothing to do with any of these facts.
They aren’t facts, again, they’re wishful thinking. I’m a long time contributor and developer and I can assure you that with things as complex as X and Wayland things would move slowly even if everybody was of the same mind, let alone in the “herding cats” style of FOSS.
Wayland has been in development for 15 years and it’s still not ready – please, it’s not, and stomping our feet and claiming otherwise won’t make it so. Another 5 years will probably see it reach a more stable state.
What do I mean by ready? Well the desktop stack [on Linux and *NIX] is extremely complex. Whenever you’re dealing with something extremely complex in software, over the years, you amass a large amount of solutions that solve real world problems. That’s what I call “ready”. Most of those solutions will be dealing with quirks and use cases which do not affect everybody equally, but they’re each crucial in their own way to a varying slice of the userbase.
Whenever you rewrite something from scratch you throw away the bulk of those quirks. It’s a common fallacy for developers to look at the shiny new thing and think that it’s better. In reality it’s worthless without the quirks, and accumulating those quirks all over again takes a long time. X has been accumulating them for 40 years. Wayland is barely scratching the surface.
The fact the protocol places and splits the burden over the various DE and WM teams will NOT help. We will need libraries that solve the same problem once instead of over and over, and most DE/WM will come to depend on those libraries. The end result will be eerily similar to X. Ironically, by the time Wayland will be done it will have spent a comparable time in development to X, and will have accumulated the same amount of baggage that people dislike about X.
What percentage of the Linux Desktop universe are you expecting will still be using X at the end of 2025?
More or less the same that’s using X right now. GNOME, KDE and the various distros will get a bloody nose trying to force Wayland through but if that’s the only way they learn, so be it.
The Steam Deck actually has one of the few use cases where Wayland actually makes sense, it’s a turnkey, highly controlled stack (both software and hardware) where users don’t have any reasons to care about what’s under the hood. I expect them to switch ASAP.
Another place where Wayland can be used straightaway is the desktop graphical login screen (which is the original reason it was created for anyway). It’s a singular application with reduced requirements and simplistic interactions.
TLDR of linked gist: wayland is not X therefore it is bad. end of.
Wayland breaks Xclip: As you said it yourself, Xclip is an X11 application, so it doesn’t work on Wayland. Of course it wouldn’t work on Wayland. With Wayland, we’re trying to prevent what happened with Xorg from happening again, or am I wrong?
also, https://github.com/bugaevc/wl-clipboard. perhaps all OP (of gist) needs is a simple shim that can convert calls to xclip to wl-copy/paste? that doesn’t seem too hard to make compared to keeping X.org alive I’d say (perhaps they should try making it if it’s that much of a problem)
Wayland breaks screensavers: Yeah, that seems to be the case.
from the dev of xscreensaver at https://www.jwz.org/blog/2023/09/wayland-and-screen-savers/ :
[…] Adding screen savers to Wayland is not simply a matter of “port the XScreenSaver daemon”, because under the Wayland model, screen blanking and locking should not be a third-party user-space app; much of the logic must be embedded into the display manager itself. This is a good thing! It is a better model than what we have under X11. […]
[…] Under X11, you run XScreenSaver, which is a user-space program that tries really hard to keep the screen locked and never crash. It is very good at this, but that it needs to try so hard in the first place is a fundamental design flaw of X11. […]
other people can comment on the parts they know about, these are two i know of off the top of my head
Who even uses screensavers these days?
businesses that want to put their logo or slogan bouncing around on monitors of inactive computers
that’s about it
I still install the MatrixGL screensaver every once in a while for shits and giggles on a new install until the gimmick wears out.
XKCD#1172 is very relevant here.
Man. That is a fair and well thought over response.
I appreciate this! Articles like this is what I’m on lemmy for!
Because calling your post a response would not do it justice enough. An article indeed.
♥️
xorg is going to die eventually. probably long after the xorg fanbois, but it will die - and wayland or something better will take its place.
A crash in the window manager takes down all running applications: Yes, because the compositor IS the server, window manager AND compositor at the same time.
Maybe not anymore in the future: https://blog.davidedmundson.co.uk/blog/qt6_wayland_robustness/
Wayland is biased towards Linux and breaks BSD
FreeBSD already has working Wayland compositors by the way.
Wayland does not work properly on Intel hardware: Again, I’m using AMD, so I can’t confirm or deny this, but considering the Intel drivers are open source, and I’ve heard about many, many improvements made on the Intel side of things, I think it would be reasonable to assume it has been fixed.
Posting this from Plasma Wayland on Intel right now. If something is broken, it’s something not apparent to me.
Dual monitor? Wayland on my intel works fine for single screen, but as soon as I plug in a 4k monitor, it gets black cube shadow like artifacts in KDE Plasma 5. A couple of kernel command line options for the module has not helped, either.
I’m fairly sure I have run this system dual-monitor though I don’t do it routinely. I’ll check sometime this weekend and let you know, if you are interested for comparison’s sake.
I most certainly am. :)
I’ve just finished watching Generation Kill on a Thinkpad T480s (i7-8650u). It was plugged into the TV, and it plus the laptops screen worked fine.
Running arch, gnome, wayland
In what kind of world is a missing feature or a broken feautre due to incomplete migration to a new ecosystem, a reason to boycott that new ecosystem?? Those are simply not valid arguments to me.
They are obviously valid arguments to say, hey, this work is not completed, is not mature enough etc. So, therefore, you stay with previous ecosystem. But to boycott it because of that? That does not make sense to me at all.
Wayland break games
The Steam Deck uses wayland so I guess that’s not true (anymore?)
Valve created gamescope, that’s a microcompositor just for games. Other Wayland compositors may still break games.
I was very sad when KDE reintroduced the concept of “primary screen”.
It used to just be the current screen, which meant that when I wanted to game or watch something on my projector, I just dragged steam or the folder with movies to the projector screen, then launched whatever I wanted, and it appeared on the screen I wanted it on.
Now I have to jerryrig kwin and a custom steam-in-gamescope Launcher to have games launch there. As a side effect, steam thinks my PC is a steam deck and therefore can’t be exited from inside of it, I have to right click the tray icon.
Horribly kludgy compared to “click launch game button on screen x, game opens on screen x”
Wayland is great! Except for all list of not-a-bugs that I’d like to see fixed. Still, I’m not going back to X, so take that how you will.
What are the not-a-bugs? Things like covering up a Wayland window will block it’s rendering thread indefinitely with no way to detect it happens to handle it. This can lock up some games, or cause you to time out in a networked application. Some Wayland core folks don’t want applications to know if their window is visible or not because it’s mild information about a user’s attention that should be private. Every game dev on the other hand is asking “WTF!?” as it causes their games to break randomly.
Another mild example is that windows cannot be raised except by the user or by launching them. This is supposed to be a mild security precaution so a program can’t pop up a legitimate looking dialog over another application and trick the user. Realistically it means that applications can’t open and focus URL in your web or file browser. Instead they have to give you a notification telling you “Firefox is Ready” and make you do it manually.
A lot of this is slowly (painfully?) changing, and the adversarial nature is a bit frustrating. Wayland fixes so many little things that I find it well worth it though, and I say that as a game developer frustrated by many of the core design decisions.
What are the not-a-bugs? Things like covering up a Wayland window will block it’s rendering thread indefinitely with no way to detect it happens to handle it. This can lock up some games, or cause you to time out in a networked application. Some Wayland core folks don’t want applications to know if their window is visible or not because it’s mild information about a user’s attention that should be private. Every game dev on the other hand is asking “WTF!?” as it causes their games to break randomly
Please don’t make up what “Wayland core folks” think. You don’t know it, and your claims are waay off.
It’s not about security. It was intended to allow the compositor to throttle apps to improve efficiency… Which of course in practice doesn’t work like this at all, because OpenGL swap buffers and Vulkan FIFO presentation modes were never intended to be used this way.
As for why that hasn’t been fixed yet, it’s not as big of a problem anymore:
- Mesa (at least for Vulkan) and Xwayland gurantee one frame per second as a minimum refresh rate
- toolkits and libraries use mailbox presentation internally and check frame callbacks themselves for when to render
- xdg shell now contains a flag for apps to know to inhibit rendering because they’re hidden. That doesn’t guarantee that presentation won’t otherwise block though
- a (set of) protocol(s) is being worked on to replace frame callbacks with a mechanism actually suited for OpenGL and Vulkan
Another mild example is that windows cannot be raised except by the user or by launching them. This is supposed to be a mild security precaution so a program can’t pop up a legitimate looking dialog over another application and trick the user. Realistically it means that applications can’t open and focus URL in your web or file browser. Instead they have to give you a notification telling you “Firefox is Ready” and make you do it manually.
That’s not even close to how activation works on Wayland, and no, it’s not just a security thing, it’s a usability thing. Apps can only raise themselves if the currently focused app gives them focus, so that random apps can’t cover up what you’re working on just cause they need to show you an ad or an “important” pop up question or whatever. If it doesn’t work for a specific app, make a bug report about it to the app.
A bit of a zombie thread, but I’m not making anything up here. The blocking issue gets discussed a lot in gamedev circles, and there are issue threads that have been locked by folks with the power to do so because they just said “no”. One of them (Maybe Sebastian Wick? I don’t remember… doesn’t really matter) gave verbatim that use case where a video service they use would stop playing videos when the browser was in the background, and that is why they won’t report . Maybe they weren’t a “core” developer, but they had the ability to say “no” and end the discussion thread.
As for it being not a problem anymore, it still occurs even on Fedora 39. The 1 second present timeout still only works for XWayland, and that’s… not a great solution. Also, realistically unless SDL2, GLFW or whatever engine a gamedev is using handles it for them they just don’t have the time to worry about what GTK, Qt, or XDG shell does. We are already supporting multiple rendering APIs, and combining that with multiple UI libraries just to get a window to draw a triangle into is a combinatorial explosion. Last I remember reading from the SDL folks, they were waiting for the functionality to appear in Wayland before they could implement it, and they weren’t expecting anything to change soon either. Speaking personally, my current game project is single player so I can just pave over the timing issues when they come up:
Long frame detected: 6463.731931 ms. Skipping ahead!
The most frustrating part to me is much more meta. You get discussions with other game devs that have heard about this stuff and they continue to think that supporting Linux is just way too much work. Sometimes they are right, but rarely for the right reasons it seems. I believe in the glorious Wayland future… I just wish it would get here a bit faster. ;) On the other hand, if we rushed it and botched it then it would never arrive at all I suppose. (sigh)
As for how window activation works, you got me there. I just heard other people discussing that one, but it did explain why on Wayland I would just get “Firefox is ready” notifications when opening links instead of just showing me the page like X did. Though I’m quite happy that it’s gone now in Fedora 39. Progress is good!
The 1 second present timeout still only works for XWayland
Oof, I thought the corresponding MR for Wayland was merged… But it was from Sebastian and after he got into a heated discussion again and started cursing, the MR got closed by someone else :|
realistically unless SDL2, GLFW or whatever engine a gamedev is using handles it for them they just don’t have the time to worry about what GTK, Qt, or XDG shell does
SDL does handle it, but only for OpenGL; it can’t do anything about Vulkan. GLFW doesn’t do anything about it either, so that is pretty annoying.
I believe in the glorious Wayland future… I just wish it would get here a bit faster
Don’t we all. Let’s hope the current upstream approach to fix this issue gets somewhere sooner than later…
all of these arguments are great and all but as an enduser: I just want things to work
I don’t care about the why’s or hows. A lot of these arguments explain and justify breakage
I am an enduser. I expect things to work, specifically I expect the programs I already use to continue working. I expect to lose no functionality
If they don’t work, then clearly its broken. If I lose functionality, Wayland clearly wasn’t ready
Wayland is ready for most people. You’re free to keep using X11 if your use case isn’t covered yet.
As someone once said: “The Technical Merits of Wayland Are Mostly Irrelevant”
But Wayland’s technical merits are relevant in a subtle way. Wayland is maintainable. Xorg isn’t. That’s it, the single most important technical merit. Everyone works on Wayland. Nobody works on Xorg. If people decide to use X11 today, their issues are wontfix with the solution to use Wayland instead. They can’t fix the issues themselves because X11 is an unmaintainable mess. Xorg is on life support with the only purpose to serve Xwayland.
for the end user, that is irrelevant
They hated her for she spoke the truth. We (DIY people) hate to acknowledge that not everyone sees value in investing as much time and energy into perfecting their workspaces as the nerds have, and would rather have their tools Just Work™ so they can get to work on the projects they do care about. I say this as someone who still gets frustrated and argumentative when my friends say they prefer spyware-ridden OSes that remove control from the end-user because they don’t require end-user micro-management to maintain and work.
X vs Wayland might as well be Grub vs rEFInd or systemd vs SysVinit to most end-users: it matters from a technical perspective, but most people just want something that will allow them to go about their business without sinking hours into getting the “correct” option to work. And it’s important to remember that we all fall on either side of this divide with some aspects of our life, even if it’s not computer-related. How often do we agonize over finding the “correct” pipe wrench when our sink is leaking, despite what the plumbing nerds would criticize you for using? Do you sink hours into picking the right books on conflict resolution when you argue with your spouse, or do you post on AITA and hope they give good advice? Do you agonize over having all the right utensils and ingredients so you can eke out the most subtle flavors from your cooking, or do you use the pan that you got at the local superstore?
I’m not a she but otherwise yes I agree
For the four groups enumerated in the article, this still is not important. It may affect them in ways they are unaware of, but you will not be able to change their minds using technical arguments at this point if they have not already been convinced by the wealth of information and support that is readily available.
