Hacker News Reader

Comment by guipsp | Hacker News Reader

XFCE is the one running late here. Gnome, kde, and even all the wlroots based compositors have been pretty solid

If you ignore things like randomly running into screen sharing problems or issues configuring XYZ thing because Gnome or whoever can't be arsed to expose it in their Wayland implementation. I keep trying Wayland and then swapping back to X11. Less issues and I never notice the things Wayland "solves", just what it breaks.

Yeah, I have the same experiences with Wayland. In fact, whenever I see it being mentioned and that it may be the default, I tend to just try to avoid the program in which it is default because I've always had issues with it. X11 works. These days are long gone where you have to modify X11 config as well, just run "nvidia-xconfig" or whatever. I do not remember the last time I had to mess around with X11. Wayland less so, as many essential features were not working. X11 has more than one clipboards as well, and I have no clue if Wayland has them, too, and we are talking about something very basic.

Indeed. I kept hearing "Wayland solves problems with two monitors at different refresh rates" But when I set up mismatching monitors, X11 didn't skip a beat (1440p native/120Hz, 1440p (being fed to a 4k native monitor)/60Hz

Conversely, the worst issue I had with dual monitors was with Wayland: Wayfire thought it was a brilliant idea to not support "window spanning two monitors" as default policy.

It feels to me like Wayland, GNOME and Systemd all come from the same sort of developer brain infection making them build vast, all-inclusive structures that are explicitly hostile to anyone who doesn't have the exact same underlying assumptions and needs.

both your monitors are being fed 60hz with x11 then right? It uses the lowest supported value of all screens

Well, the monitor itself says it's being fed 120Hz in its status popup, I don't think X11 is smart enough to lie in that way.

Your monitor says it's in 120hz mode but it's not actually being fed 120hz

  I never notice the things Wayland "solves", just what it breaks.

I wish I could say otherwise - but this has 100% been my experience as well across multiple distros and is 100% why I still run X11 today.

some value of "solid" that ignores machines with vmgfx or nvidia modules.

An argument where this is a problem with the protocol instead of uncompliant vendors is disingenuous.

The protocol might be good, but my hardware is not supported by wlroots. Whether this is the fault of upstream or the hardware vendor does not matter. I cannot run wlroots, ever. Period.

It does matter, because one post before you felt entitled to put the blame on the protocol. Nuance is pretty important when you take into account the difference in amount of resources available to the two groups.

Don't know which post you are referring to. We must be reading different threads.

Maybe I'm misunderstanding you when you argue against desktop environments and wlroots compositors having "solid" wayland implementations due to not working under nvidia cards. If that's the case I might argue that you could present your point in a less terse manner.

Reply on news.ycombinator.com