Live data from Hacker News

Wayland vs. X – Overview

wayland.freedesktop.org

31–40 of 186 posts

Re: Wayland vs. X – Overview

#31
post #3
post #2

[flagged]

Has Wayland fixed the fact that compositing sucks by definition?

"combine (two or more images) to make a single picture, especially electronically" ... sucks?

I can't even begin to think how you would present multiple windows to a user if you didn't composite them into a single image. Even if you are doing a 3D virtual desktop, you still have to composite the layers down to 2 single slightly offset images.

Re: Wayland vs. X – Overview

#32
post #20
post #10

I don't know what I'm doing wrong with Wayland. I have a cheap Linux laptop, with built in graphics. And Wayland works perfectly. I can run multiple monitors with one of them rotated. When I tried that with X I got lots of juddery tearing. I can take screenshots and share my screens via video calls. But everyone says it doesn't work due to security. I have fractional scaling and it doesn't seem to burn out my CPU or…

You only get one chance to make a good first impression. Wayland is probably much better than when I tried it in 2019 but all I remember is the 2019 experience. I think a lot of people are in the same boat.

Really? I can’t help but notice that nobody is describing X as if it hasn’t improved since XFree86 in the 90s so perhaps it is possible for technical professionals to update their understanding?

Re: Wayland vs. X – Overview

#33
post #18
post #10

I don't know what I'm doing wrong with Wayland. I have a cheap Linux laptop, with built in graphics. And Wayland works perfectly. I can run multiple monitors with one of them rotated. When I tried that with X I got lots of juddery tearing. I can take screenshots and share my screens via video calls. But everyone says it doesn't work due to security. I have fractional scaling and it doesn't seem to burn out my CPU or…

I literally cannot get Wayland working. Everything is broken. It's slow, the fractional scaling doesn't work, full screening apps like vlc or games turn off my monitors, the distro installer crashes, playing a youtube video makes my laptop heat up like crazy, one time a display change made my laptop's screen flicker so hard that it persisted after I restored the settings, another time it turned my monitor's bright re…

Outside of using Wayland, do you do much 3D rendering?

The symptoms you describe almost sound like a dying 3D graphics card (or 3D graphics card with misconfigured drivers). I wonder if Wayland is requiring the 3D layer to do its compositing and other window engines don't?

Re: Wayland vs. X – Overview

#34
post #2

[flagged]

Isn't only the transport layer of X insecure? That could be swapped out with another layer. With Wayland you have to use VNC which is fine for local networks, but not for remote ones.

I believe there's work ongoing to upgrade to using H264 using MS's RDP protocol rather than VNC and getting that to work under wayland. That's waaaay better than X forwarding or VNC. if I recall correctly you've also got it backwards - I seem to recall X forwarding is much worse for higher latency networks than VNC.

Re: Wayland vs. X – Overview

#35
post #7

Earlier quoted context omitted.

From what I understand, and I’m no expert on this, X pretty much broke application sandboxing. X’s design was inherently insecure in the context of modern OS security practices.

I think you're phrasing that incorrectly. There was no application sandboxing for X to break. And you can't build sandboxing atop X. You speak as if application sandboxing within the ever existed in the past... Not that people tried to build it and X doesn't play well with it.

I don't profess to have any deep knowledge of X11 or Wayland, but I don't understand how sandboxing can't work in X11. XWayland exists and it is either non-sandboxed (hence Wayland doesn't add any security benefit) or it is. And if it is it means that X can be sandboxed and it should be possible to run XonX sandboxes. Something like xnest.

Re: Wayland vs. X – Overview

#36

Earlier quoted context omitted.

Isn't only the transport layer of X insecure? That could be swapped out with another layer. With Wayland you have to use VNC which is fine for local networks, but not for remote ones.

My understanding is that any app which has access to X (so any windowed app) had full access to all other apps which have access. So, any app with a window can read the input from any other app on the same system, e.g. your sudo password. Or, take a screenshot of your bank info in Firefox.

The thing is a 'day 1' feature everyone hacks back in is clipboard sharing and screen share, each of which remove a decent chunk of these protections. Each essentially grants access to another apps data.

Plus the attack angle is someone having permission to execute apps on your machine, there's plenty of other nasty things they could do.

Re: Wayland vs. X – Overview

#37
post #10

I don't know what I'm doing wrong with Wayland. I have a cheap Linux laptop, with built in graphics. And Wayland works perfectly. I can run multiple monitors with one of them rotated. When I tried that with X I got lots of juddery tearing. I can take screenshots and share my screens via video calls. But everyone says it doesn't work due to security. I have fractional scaling and it doesn't seem to burn out my CPU or…

I think the place you get into trouble is when you try and DIY the config. I'm using Fedora and everything works perfectly out of the box. But when I was using arch and was trying out Sway (i3 + wayland) I was constantly running into issues.

Re: Wayland vs. X – Overview

#38
post #20
post #10

I don't know what I'm doing wrong with Wayland. I have a cheap Linux laptop, with built in graphics. And Wayland works perfectly. I can run multiple monitors with one of them rotated. When I tried that with X I got lots of juddery tearing. I can take screenshots and share my screens via video calls. But everyone says it doesn't work due to security. I have fractional scaling and it doesn't seem to burn out my CPU or…

You only get one chance to make a good first impression. Wayland is probably much better than when I tried it in 2019 but all I remember is the 2019 experience. I think a lot of people are in the same boat.

I wonder if you asked people their feelings about 1) Wayland, and 2) systemd, whether or not sentiment would be highly correlated. My first impression of both was when I had a problem.

Re: Wayland vs. X – Overview

#39
post #10

I don't know what I'm doing wrong with Wayland. I have a cheap Linux laptop, with built in graphics. And Wayland works perfectly. I can run multiple monitors with one of them rotated. When I tried that with X I got lots of juddery tearing. I can take screenshots and share my screens via video calls. But everyone says it doesn't work due to security. I have fractional scaling and it doesn't seem to burn out my CPU or…

You probably need an Nvidia graphics card. That was the source of all my problems when I first tried it. I dumped that shit and been using Intel graphics and Wayland (sway) happily since 2019.

Re: Wayland vs. X – Overview

#40
post #10

I don't know what I'm doing wrong with Wayland. I have a cheap Linux laptop, with built in graphics. And Wayland works perfectly. I can run multiple monitors with one of them rotated. When I tried that with X I got lots of juddery tearing. I can take screenshots and share my screens via video calls. But everyone says it doesn't work due to security. I have fractional scaling and it doesn't seem to burn out my CPU or…

I think the place you get into trouble is when you try and DIY the config. I'm using Fedora and everything works perfectly out of the box. But when I was using arch and was trying out Sway (i3 + wayland) I was constantly running into issues.

Odd, I use Arch (well, EndeavourOS) with Sway and have experienced no problems. Quite on the contrary, my setup with a high-DPI laptop + external monitors is far nicer with Wayland than with X.
Post reply on HN