zlacker

>>throwa+(OP)
Well-known developer Enrico Weigelt just forked the X server from freedesktop.org after getting the boot [0].

[0] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...

[1] https://github.com/X11Libre/xserver/commits/xlibre/prepare/

>>throwa+9
“Getting the boot” is rather vague. Is there any more information anywhere, background, &c.?

My general impression (quite possibly incorrect) was that X.Org Server is largely treated as “done”, making only bugfixes and such these days.

>>chrism+04
From the readme:

> That fork was necessary since toxic elements within Xorg projects, moles from certian big corp are boycotting any substantial work on Xorg, in order to destroy the project, to elimitate competition of their own products. (classic "embrace, extend, extinguish" tactics)

> This is an independent project, not at all affiliated with BigTech or any of their subsidiaries or tax evasion tools, nor any political activists groups, state actors, etc. It's explicitly free of any "DEI" or similar discriminatory policies. Anybody who's treating others nicely is welcomed.

>>JimDab+E4
> moles from certian big corp are boycotting any substantial work on Xorg, in order to destroy the project

That's what I've always thought. The "X11 developers" pushing for Wayland weren't original developers so much as RedHat "maintainers," who (understandably) wanted a frontier to explore rather than janitorial work. All I know for certain is that X11 (even as of 15 years ago) mostly worked, while Wayland of 2025 is still full of headaches & breakages.

>>hello_+B5
X did not "just work" for me 10 years ago, and neither is Wayland "still full of headaches and breakages"

I've had no substantial problems because of Wayland in the last, like, 5 years.

>>dralle+w7
2016-01-23 https://github.com/MaartenBaert/ssr/issues/431

2019-01-04 (only took 3 1/2 years to resolve!) https://github.com/flathub/us.zoom.Zoom/issues/22

2020-03-07 https://github.com/vkohaupt/vokoscreenNG/issues/51

2020-03-07 https://github.com/obsproject/obs-studio/issues/2471

2020-03-24 https://github.com/jitsi/jitsi-meet/issues/6389

2023-09 https://www.jwz.org/blog/2023/09/wayland-and-screen-savers/

2023-11-17 https://github.com/raspberrypi/bookworm-feedback/issues/149

>>hello_+G9
More than 2/3rds of your examples are from over 5 years ago, and one of the links is to a site that replaces its content with an image of a testicle when hotlinked from HN.

>>moron4+aa
> More than 2/3rds of your examples are from over 5 years ago

Exactly! If you scroll to the bottom of each one, you will see that most are either a) still open, or b) abandoned (too hard or impossible), then closed as stale.

> image of a testicle when hotlinked from HN

Rightly so.

>>hello_+va
One open issue has a comment at the bottom saying that the issue is fixed and was an issue with Mutter. There's no evidence to think that it was ever a "wayland" issue.

One open issue has had locked comments for 5 years. It's probably fixed but nobody has bothered to close it.

Most of rest were not actually "wayland" issues, either. Yes, someone's hobby project screen recorder might not get updated to work with wayland, but there's dozens of those, feels a bit unfair to ignore that there's alternatives.