←back to thread

49 points 1una | 3 comments | | HN request time: 0.651s | source
Show context
not_your_vase ◴[] No.35928051[source]
> Yes, not every random app and feature you use on Xorg will have a Wayland equivalent. Deal with it.

In general this sentence is why the Year of Desktop Linux won't come in this millennia. Not only XOrg vs Wayland. Many such cases. Sad!

replies(8): >>35928066 #>>35928112 #>>35928157 #>>35928221 #>>35928227 #>>35928231 #>>35928305 #>>35928559 #
imiric ◴[] No.35928227[source]
That quote is exactly why Linux will never reach mainstream adoption. Arrogant Linux developers who pick a hill to die on because they feel technology X is "better". They refuse to acknowledge that none of it matters if it negatively impacts user experience. This "deal with it" attitude is beyond obnoxious.

User experience is ALL that matters. Apple has this ingrained in their ethos. While the OSS communities are bickering over X vs Y, they chose to pick what's usable and polish it until it delivered great UX.

Last time I checked, Wayland was broken in fundamental ways on my NixOS/KDE machine. So I went back to Xorg, that for all its ancient faults, delivers a better UX _today_. I'll keep trying Wayland every few months, and when it becomes an improvement, I'll consider switching to it. No, I won't "deal with it". Why don't YOU fix it?*

*If you tell me that it's not up to you, but to application developers to add support for Wayland, I'll drop kick your sticker-infested laptop, and curse whoever came up with this ridiculous system.

replies(2): >>35928649 #>>35928996 #
rektide ◴[] No.35928996[source]
This feels like a nightmare conflict. I would be so less interested in trying to drive open source tech forward if I had to actually deal with such as this.

Do you have any open bug reports you can point to for "Wayland" not working? Which compositor were you try to use?

This all reminds me so much of ESM Vs cjs. Tech sometimes direly needs a kick in the ass. The situation cannot hold with something old & not good & the new works for most people, but also there's 1% valid problems. The world deserves to be able to eventually move on. The world can be bold & progressive & make changes, it should, and we should expect more of each other about being timely, about doing thr right thing, about making shifts. But we become so trapped by such resistance & unadaption, by staying where we are. Progress is a spirit I think should be Integral to open society & especially open source, but people don't see themselves as part of the bigger thing, they view themselves as merely at ends.

replies(2): >>35929424 #>>35932839 #
1. zerker2000 ◴[] No.35932839[source]
pulling the concrete friction-report referenced in the reply https://news.ycombinator.com/item?id=35316159

(these are not necessarily the same issues, but at least similar-sounding ones I found by googling)

• widgets opening in wrong place: https://bugs.kde.org/show_bug.cgi?id=459188

• ignoring icon size configurations: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/i..., closed as wontfix

• on touchscreen menus open wherever you left the cursor: https://bugs.kde.org/show_bug.cgi?id=406025, more info in https://github.com/PeterCxy/evdev-right-click-emulation/issu...

• cursor framerate issues: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1827 maybe, it's in the gnome issue tracker but described as wayland-specific, so might also be happening on KDE

• firefox using wrong screen's DPI: https://bugzilla.mozilla.org/show_bug.cgi?id=1632829, resolved by original reporter but last comment is a repro from someone else. also reported in https://github.com/flatpak/flatpak/issues/5300 but closed as "wrong bug tracker"

• fullscreening a video rotates it from portrait to landscape: https://bugzilla.mozilla.org/show_bug.cgi?id=1600962 possibly, https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/190522... possibly

In general wayland seems too buggy for major software like firefox to use it by default, per https://askubuntu.com/questions/1409389/why-doesnt-firefox-r...

Impressive list to hit in only 5 minutes!

replies(1): >>35933319 #
2. imiric ◴[] No.35933319[source]
Haha I appreciate the sleuthing, and thanks for the links! <3

Some of those might be the bugs I experienced, but then again, some of them claim to be fixed years ago, and I was running a fully up-to-date NixOS unstable (rolling release) system.

Reporting an issue in an OSS project is a great freedom that users have, but it involves so many steps, especially in these complex environments, that it's often not worth the effort. Even if you manage to figure out which component is misbehaving, to search if there's an already open bug report, and take the time to create one if not, there's a chance of running into hostility and WONTFIX responses.

> Impressive list to hit in only 5 minutes!

All it took was logging in, launching Firefox and playing a video. If these issues were so obvious in 5 minutes, I couldn't imagine how many there would be had I used the system for longer. Switching back to Xorg was the quickest fix to my workflow. Besides, I figured that since these issues were so obvious that they were already known. I was just befuddled as to why they remain so prominent given that Wayland is already 15 years old, and there are mainstream distros offering it as an alternative, or switching altogether to it.

replies(1): >>35942987 #
3. ◴[] No.35942987[source]