Most active commenters
  • mort96(4)
  • michaelmrose(3)

←back to thread

49 points 1una | 12 comments | | HN request time: 0.651s | source | bottom
Show context
psanford ◴[] No.35928220[source]
I'm an Asahi user and I back the project on Patreon. I also use xorg and don't have any plans on switching to Wayland any time soon. My reason is simple, there isn't an equivalent to xmonad on Wayland (nope sway isn't an equivalent for me).

I don't have any issue with Asahi focusing on Wayland first. But this attitude doesn't make me feel great. Is it really so difficult to have a little bit of empathy for your end users?

replies(3): >>35928318 #>>35928348 #>>35928745 #
gjsman-1000 ◴[] No.35928318[source]
> Is it really so difficult to have a little bit of empathy for your end users?

That’s easy to say if you’ve never worked on Xorg. The codebase is one of the worst in existence, few people fully understand it, and fixing bugs in it is a modern Sisyphean wheel.

replies(1): >>35928346 #
1. psanford ◴[] No.35928346[source]
I'm really not asking for that. I'm asking for communication that doesn't feel dismissive.
replies(1): >>35928395 #
2. gjsman-1000 ◴[] No.35928395[source]
I think it’s more exhaustion at the fact users do not want to move on; and yet, this is Linux in 2023.

- GNOME is Wayland by default

- Red Hat has announced Xorg is depreciated. A big deal considering they were basically keeping Xorg on life support single-handedly. Without Red Hat, there’s basically nobody working on it anymore.

- KDE Plasma 6 has announced Wayland is default now.

At some point, it becomes like a user complaining that OS/2 is no longer supported. It’s dead, X11 is older than OS/2 (June 1984!), we are all collectively exhausted, time to move on.

If xmonad doesn’t work for your system; take it up with them.

replies(3): >>35929494 #>>35930029 #>>35935974 #
3. t-3 ◴[] No.35929494[source]
What does the origin date of X11 have to do with anything? Doesn't look abandoned or dead: https://gitlab.freedesktop.org/xorg/xserver/-/commits/master
replies(1): >>35936322 #
4. yjftsjthsd-h ◴[] No.35930029[source]
> exhaustion at the fact users do not want to move on

The users will move on when the replacement is unambiguously better, and/or at least has feature parity. Telling someone to throw out their working setup is a lot of why Wayland is viewed by some people with derision.

5. michaelmrose ◴[] No.35935974[source]
It's unreasonable to expect an X window manager developer to both maintain their WM and invest in writing a compositor a MUCH larger project. It's vastly easier for everyone involved to just keep using X. The age of the original X protocol is completely irrelevant to the discussion. Unlike OS/2 it's a living feature complete project. It doesn't spoil like cabbage.
replies(1): >>35936316 #
6. mort96 ◴[] No.35936316{3}[source]
Writing a Wayland compositor on top of wlroots is probably a larger project than writing a window manager for X. But it's not orders of magnitude, wlroots handles a whole lot of the dirty work for you.

> The X protocol [...] doesn't spoil like cabbage.

It actually does. The protocol doesn't handle things we expect from modern hardware and software. And the implementation certainly rots away as the rest of the software ecosystem changes in ways which will slowly make Xorg more and more broken. Drivers will change in ways which expose Xorg bugs. GUI toolkits will introduce bugs in their X backends and introduce new features which don't work on their X backend. Nobody maintains X anymore, and something like a display server in a rapidly changing software and hardware ecosystem requires maintenance to keep functioning.

None of this is to say the Xmonad developer should spend time rewriting their project to use wlroots instead of X. But as long as it requires X, it's living om borrowed time.

replies(1): >>35939721 #
7. mort96 ◴[] No.35936322{3}[source]
Look again. Almost all those commits are for XWayland.

XWayland is not going away. X as a display server is more or less abandoned.

replies(1): >>35936705 #
8. ◴[] No.35936705{4}[source]
9. michaelmrose ◴[] No.35939721{4}[source]
There is not one singular meaningful app or feature that doesn't work on X at this point.
replies(1): >>35945057 #
10. mort96 ◴[] No.35945057{5}[source]
Screen tearing is more or less unavoidable on X. I've had tearing issues on Nvidia, Intel and AMD.

Avoiding jank is also more or less impossible on X. There is no substitute for Wayland's "every frame is perfect" model.

Oh, and you can't connect a high DPI screen and a low DPI screen at the same time with X; to the degree that DPI scaling works at all, it's one global setting so you get to choose whether stuff should be absurdly big on your low DPI monitor or absurdly small on your high DPI monitor.

replies(1): >>35945077 #
11. michaelmrose ◴[] No.35945077{6}[source]
I didn't have that problem is 2003 nor today.
replies(1): >>35945253 #
12. mort96 ◴[] No.35945253{7}[source]
Good for you! Doesn't make them not problems.