Wayland breaks your bad software
orowith2os.gitlab.io
orowith2os.gitlab.io
Plus, not all of these comments really line up in my opinion:
> Just use Nouveau if you want to do anything with Xwayland, and you don’t have several GPUs.
No? Nouveau is an awful experience on Wayland if you intend to get more than 30% of your GPU's performance, doubly so for a recent GPU. The benchmarks are atrocious: https://www.phoronix.com/review/nvidia-nouveau-2019
Not sure where that one's coming from. I've been using Java apps in xWayland on Nvidia native drivers without issue for a while now.
> Wayland technically has nothing to do with screensharing - this is all handled separately, in PipeWire and xdg-desktop-portal.
> Look at Xorg, and you get a worse UX
...because it's 30 years old, and (like Wayland) was not designed with screensharing in mind?
There's nothing that stops you from using PipeWire and XDG portals to get roughly the same experience on x11. It would suck for other reasons, but this is a really strange point to highlight.
> Application development PoV
> Hell.
It's really not. I've written software that unconsciously targeted both x11 and Wayland perfectly fine. Even native applications in xWayland run... like native.
I'd keep going but I'd rather not. Their article seems to be hyperbolic and overly hypocritical.
To expand on this, nouveau is cryptographically handicapped by nvidias decision to lock reclocking and power management API's behind cryptographic firmware signing required to execute in FALCON High-Sec mode processors since the GTX 9xx series (Maxwell I think?) and on.
Even if someone cracks that nut; which they have, nouveau can't really reap the benefits of it due to the DMCA anti-circumventiom violation that leveraging that nut cracking would likely entail.
Therefore, nouveau is quite literally cut off at the lnees by Nvidia, and their decision to lock away those critical API calls where no fully compliant, "good-faith" FLOSS dev can actually get at them.
So saying nouveau is terrible is a huge misnomer/misconception, as it is entirely Nvidia that are responsible for the inability of anyone else but them to write legally unencumbered firmware to leverage the full functionality of the hardware boards they sell.
Going and placing the blame for "terribleness" on X11 vs. Wayland, then completely mischaracterizing the situation around nouveau, which os in the most heartbreaking state as a project that I can possibly imagine I tend to take as a glaring indication that someone knows nothing about the stack beneath them.
Wayland vs. x11 is honestly one of those things that infuriates me in the sense that instead of looking at X11 for what it was; a godsend in terms of providing a graphical desktop environment in a network transparent way, on machines that often were spec'd in the M prefix in terms of RAM and processor cycles, vs Wayland, a project born out of an impetus (from automotive and embedded systems groups if I recall the origin story) to have a quicker graphics environment spin-up on bespoke hardware.
I'll give props where props are due, but I still find the X Protocol to be a far from obsolete protocol. Even of graphics ptogramming isn't my bag, and counts itself as one of the chief items in my "bag of crap I haven't had time to sit down and really read/dig through yet
[1]https://hexkyz.blogspot.com/2021/11/je-ne-sais-quoi-falcons-...
> So saying nouveau is terrible is a huge misnomer/misconception
I'm not trying to misrepresent them at all. The performance experience is miserable, and you're wasting power to run it (especially on newer systems). The software effort is noble, and Nvidia is terrible for being so mean and stingy with their hardware. That being said, they ship a perfectly usable driver that I've daily driven, on Wayland, for years. Bringing DEs into the equation is just so I can refute the lousy argument that people should be using Nouveau on a daily basis. Unless you have an ideological objection, the proprietary driver is unfortunately the best no-hassle experience for Nvidia GPUs on Linux. That's the sad part.
> I still find the X Protocol to be a far from obsolete protocol.
That's very much what got me to write my original comment. The original article feels weird and combative, like x11 and Wayland are competing protocols. It's dead, Jim.
I mention this in the article.
> ...because it's 30 years old, and (like Wayland) was not designed with screensharing in mind?
And unlike Xorg, Wayland didn't have it hacked on. There was an actually decent library available (PipeWire) and portals that made it work nicely, and fit with the vision of the Wayland developers.
> It's really not. I've written software that unconsciously targeted both x11 and Wayland perfectly fine. Even native applications in xWayland run... like native.
I am interacting with the X protocol and trying to sort it all out and no, it is NOT perfectly fine. It's enough of a hell that I'm considering leaving the heavy lifting to third party libraries like SDL, Winit, and Smithay.
Forget performance, I get display corruption and crashes on both Wayland and X/kwin with compositing enabled if I use Nouveau. This is on a GTX 1050 Ti. I should point out that the issues Nouveau went from daily occurrences to a bit less than weekly over the time I've owned the card, but I'd like to not have to restart my desktop that often.
Nowhere does it list the fact that on 3 out of 4 of the machines I have tried it on, KDE cannot even get to the point of rendering a desktop on Wayland. Each time I have dug into it, it has turned out to be a video driver issue (and indeed on 2 of the 3 non-working machines, I also need to disable compositing in Xorg for reliable video display). I suppose "Wayland breaks your bad software" also applies to bad video drivers.
Another point is that Xorg is dying because the people who were previously keeping it alive switched to working on Wayland; the only comparison we can actually do is comparing Wayland today to Xorg today. We would like to compare it to Xorg in a world in which Xorg development kept moving forward, but counterfactuals are hard. To be fair, I have heard from some people that the Xorg code is bad enough that if hacking on Wayland weren't an option, the developers in question would reject technology and live in the wild rather than continuing to maintain Xorg.
If Xorg development continued, we would still end up with Wayland, just under a slightly different name. You can only keep the X11 protocol, even with extensions, going for so long, and we've long since reached its expiration date.
I'm not sure where does the author draw this conclusion from, but HDR has been around since at least 15 years ago and it's pretty much everywhere at this point: TVs, console, phones, portable gaming devices, laptops, tablet, you name it. On Windows and Mac, iOS, Android, the several OSes for TVs...
> HDR is a pretty new thing. It’s still a child everywhere but TVs and consoles. macOS is probably the most usable platform in that regard. Windows supports it too, but the experience can be iffy, as well as their automatic SDR -> HDR conversion.
Many things have been around for years, but development focus and people actually using those things is a different story.