zlacker

[return to "The X.Org Server just got forked (announcing XLibre)"]
1. throwa+9[view] [source] 2025-06-06 10:37:14
>>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/

◧◩
2. chrism+04[view] [source] 2025-06-06 11:25:46
>>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.

◧◩◪
3. JimDab+E4[view] [source] 2025-06-06 11:32:36
>>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.

◧◩◪◨
4. hello_+B5[view] [source] 2025-06-06 11:42:19
>>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.

◧◩◪◨⬒
5. dralle+w7[view] [source] 2025-06-06 12:01:18
>>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.

◧◩◪◨⬒⬓
6. bluefl+w8[view] [source] 2025-06-06 12:09:14
>>dralle+w7
Nvidia, vmxgfx. I would run wayland if i could.
◧◩◪◨⬒⬓⬔
7. marius+Fk[view] [source] 2025-06-06 13:37:02
>>bluefl+w8
> I would run wayland if i could.

You can if you stop buying nvidia. The problem with missing drivers is principally the fault of the hardware vendor not of the kernel community.

◧◩◪◨⬒⬓⬔⧯
8. bluefl+xF1[view] [source] 2025-06-06 23:03:27
>>marius+Fk
You know what runs on these platforms? Xorg.
◧◩◪◨⬒⬓⬔⧯▣
9. marius+U72[view] [source] 2025-06-07 05:47:48
>>bluefl+xF1
Perfectly true. What I was getting at is that you should direct your frustration to the correct place: not with the efforts of wayland and kernel devs but with the stubbornness of the hardware vendors that don't want to make their code public, and in the case of nvidia, (or) use the same driver building blocks that the kernel community recommended.
◧◩◪◨⬒⬓⬔⧯▣▦
10. antiso+lh4[view] [source] 2025-06-08 10:10:03
>>marius+U72
What you seem to be missing is that a whole lot of people don't actually have any "frustration", except when people come along claiming that their new windowing system is "totally ready... except it doesn't support any good hardware".

For people like us, X works just fine, with our nvidia cards, and we're not actually interested in the philosophical purity of who's fault it is that wayland doesn't work with our nvidia cards. If we cared about that kind of stuff so deeply, we wouldn't be using the proprietary drivers.

IF you want people to switch to wayland, then solving all those edge cases, and making it work properly with proprietary graphics drivers (or maybe getting nvidia et al to open their code, good luck with that) is your problem.

[go to top]