Live data from Hacker News

The technical merits of Wayland are mostly irrelevant

utcc.utoronto.ca

131–140 of 203 posts

Re: The technical merits of Wayland are mostly irrelevant

#131

I feel like one of the biggest issues with Wayland is that the 'mob energy' of the people who really thought who could slay the Microsoft Dragon, and make 'Year of the Linux Desktop' happen just isn't there anymore. These people made things like drawing tablet support on X, as well as had the power of fixing all the little weird use cases you'd need for a truly large user base. It's really funny that open source is b…

Nailed it.

Seems like forever, the Wayland people are really out here thinking that 100 developers in a trenchcoat can be the same as a Steve Jobs, when, no -- please just make sure all the old stuff works.

Re: The technical merits of Wayland are mostly irrelevant

#133
post #55

This article, like many, ignores the reality that lots of setups -- especially workstations with several high-res monitors -- do not work at all, or work with enormous jank-ass caveats even bigger than the ones that come with using Wayland. (Which I admit are also hellacious in may cases.) Case in point: I have to use Wayland, because otherwise my Linux machine just can't reasonably drive my monitors (one 8K, three 4…

> (one 8K, three 4K, and one high-refresh-rate 1440p portable) More power to you, pushing the limits. But frankly with this setup, you are in a tiny minority. What is your use case? What is the technical reason that this works on Wayland but not X? I've had one 4K screen since 2018, never had a problem. Other than the fact that older applications don't respect high-dpi so need manual tweaking, or need to be replaced.

My use case is just regular computer use (browsers/photos/email/3D CAD/video editing), and my day job as a software engineer.

I'm just one of those people who likes multiple monitors (one of the 4K is a TV on the wall, so often not in use).

I would like all the monitors to be 8K, but that's just too expensive for now).

Re: The technical merits of Wayland are mostly irrelevant

#134

The security benefits are massive. X allows *every* application to take screenshots of the whole screen. 40 comments and nobody pointed out this benefit...

Doesn't Wayland WMs have to break those "security benefits" constantly to just be able to take a screenshot?

Sensitive features like screenshots, input methods, screen locking and whatnot are behind extensions (or portals). I'm not familiar with the state of GNOME/KDE/Flatpak, but at least on the wlroots side of things it is true that currently these extensions are enabled and accessible by any process that can talk to the Wayland socket (breaking those security benefits, as you say). This is changing with protocols such as security-context that allow a sandbox engine like Flatpak (or your custom scripts) to restrict what features apps can use. (so your browser can't register an input method, or some random app can't lock the screen)

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...

https://github.com/swaywm/sway/pull/7648

https://github.com/flatpak/flatpak/pull/4920

Re: The technical merits of Wayland are mostly irrelevant

#135

This might be a hot take, but you'll have to take X from my cold, dead hands. Or at least until things start breaking, or maybe until Wayland has e.g. stellar HDR support and I'll get a nice OLED monitor. Otherwise, no dice. I know that X is a crusty old spawn of Cthulhu; but honestly, I don't really care? It just works! I set up my system 10 years ago with how the UI works (including my window manager), and it stabl…

Is screen tear something that can be avoided in X11? That's mostly the only reason why I bother with Wayland

Yes, using a compositor. I use kwin's compositing with Intel graphics, no tearing.

Re: The technical merits of Wayland are mostly irrelevant

#136
post #55

This article, like many, ignores the reality that lots of setups -- especially workstations with several high-res monitors -- do not work at all, or work with enormous jank-ass caveats even bigger than the ones that come with using Wayland. (Which I admit are also hellacious in may cases.) Case in point: I have to use Wayland, because otherwise my Linux machine just can't reasonably drive my monitors (one 8K, three 4…

> Upon logging into any modern Linux, like Fedora or Ubuttnu or whatever, X will freak out, jank out with its crank out, and -- only if I am lucky -- finally show the desktop.

...and there goes my coffee all over my HiDPI display. thanks for the laugh. I guess.

Re: The technical merits of Wayland are mostly irrelevant

#137
post #115

Earlier quoted context omitted.

> VNC does something entirely different from this -- it just shares an existing desktop remotely rather than providing a unique independent desktop. Actually, not necessarily; you can use Xvnc to achieve this with X+VNC. It's an X server that serves over VNC. Can Wayland do this? Yes! But, the problem is that there is no singular Wayland "display server". This is both a big strength and big weakness of Wayland. In th…

> Can Wayland do this? Yes! Interesting. I remember asking some Wayland devs a few years back about this and they said this use case would never be supported. I'm glad that's changed! It means that if the day comes that I have to use Wayland, I won't necessarily lose functionality. (Just for clarity, I'm not opposed to Wayland if it can do what I want. But I'm not excited by it, either, because the benefits it does p…

Yeah, as you may gather from my first post, I am not advocating anyone to switch if there's nothing in Wayland for them. But at least with wlroots-based compositors (a decent number of them, but notably not GNOME and KDE which use Mutter and Kwin respectively,) you can definitely do this sort of thing relatively easily. It'd probably be a good idea if every compositor got on the same page here so that the experience is consistent. I'm not sure how to do this kind of thing with every compositor.

Re: The technical merits of Wayland are mostly irrelevant

#138
post #119

Earlier quoted context omitted.

I just had to look it up; Wayland has been around for 14 years already. How much software takes 14 years and still isn't stable? How big and / or complicated is this problem and the codebase anyway?

PulseAudio is still not there after 19 years.

On the other hand, PipeWire is?

Re: The technical merits of Wayland are mostly irrelevant

#139
post #84

No one really cares deeply about what a compositor or low level windowing system does since it shouldn't be a thing you notice. Desktop OS'es have simple criteria and user expectations: they should work no worse than Windows or OS X, and that's it. Whether you need Wayland or not to reach feature and performance parity with commercial desktop OSes isn't very interesting to people, only that you actually do.

I care. I've only recently learned about them, and I'm not in any way an expert on any of this, but from what I understand, they do an important job, and the way they do that in X11 either hurts gaming performance or makes them unstable. When I'm playing Cyberpunk 2077, occasionally the game crashes (hasn't happened often, but a few times), and when it does, the compositor fails until I kill the CP process. And while…

I haven't tried Cyberpunk 2077, but I play a bit of Minecraft and from my testing KDE's Wayland implementation has about a 25% FPS penalty at least. I keep the FPS capped at 60fps, my display speed, and with X11/kwin the game can maintain that in all but extreme circumstances (e.g. breeding thousands of mobs, or https://bugs.mojang.com/browse/MC-226966 (ludicrous bug btw)) With Wayland in the same parts of the map my FPS will be in the 40s. This is with numerous performance mods; without those it's much worse.

It's not something I care to spend time debugging, since Wayland doesn't give me any other reason to chose it anyway. But I still try it once or twice a year to see if it has improved, and after several years of this I'm starting to think it never will.

Re: The technical merits of Wayland are mostly irrelevant

#140
post #55

This article, like many, ignores the reality that lots of setups -- especially workstations with several high-res monitors -- do not work at all, or work with enormous jank-ass caveats even bigger than the ones that come with using Wayland. (Which I admit are also hellacious in may cases.) Case in point: I have to use Wayland, because otherwise my Linux machine just can't reasonably drive my monitors (one 8K, three 4…

> And there is AFAIK no distro that supports mixed 8K/4K/2K monitors with working font scaling using X.

AFAIK x11 doesn't support this - at least assuming you want fractional scaling.

> Unfortunately, my workflow also requires being able to do remote desktop, and share my screen during remote meetings. Which doesn't work a blood clot on Wayland yet.

Last i ran Linux - screen sharing worked fine with PipeWire and chromium - is that no longer the case?

Post reply on HN