This dude is a hopeless weirdo, who mindlessly refactors for no real reason, and breaks stuff.
The insane conspiracy minded anti-big tech aspect is deeply disturbing. Replying to some of the most respectable food hard working nice people on the planet who have carried huge X subsystems forward for decades with love and care with just frothing madness. There aren't words for the scorn this insanity & batshit deserve.
This comment and first reply have some solid other discussion. https://news.ycombinator.com/item?id=44303328
I frelling love the reg, love me a good rag. It was intensely intensely disappointing to see they carrying so much water for this deeply problematic antisocial troublemaker.
Xlibre may just be successful despite weigelts opinions (and maybe even attract some supporters because of them) and the only way for Xorg/wayland to counter the rise of Xlibre is to address the concerns and not to write off Xlibre because of weigelt.
Summary
Replace the X.Org X11 Xserver (xorg-x11-xserver) with the X11Libre (XLibre) Xserver, an actively maintained fork.
Disclaimer
The Change Owner does NOT share or endorse upstream's political views! Given that those can be found even in the upstream project-wide README.md, the Change Owner feels obliged to make this clarification.Have fun with the Xlibre community.
The fact that the proposer has to include such disclaimer also says a lot about the Xlibre upstream community.
as someone who is firmly in the wayland camp i believe that this indicates significant grief that people who join Xlibre despite its anti DEI stance have with wayland that wayland devs should take note and not just dismiss the entire Xlibre community as a bunch misguided individuals.
Noted changes with XLibre 25.0 include:
a) Xnamespace extension: a novel approach for isolating clients from different security domains (eg. containers) into separate X11 namespaces, where they can't hurt each other
that seems significant, I wonder why xorg hasn't implemented something like it so far.Otherwise we would probably have had this years ago.
Long live Xorg, I mean Xlibre
https://news.ycombinator.com/item?id=44302650
The X.Org Server just got forked (announcing XLibre)
em-bee•5mo ago
this article talks about the effect of the fork on Xorg itself. which is a very different topic, and one that is worth talking about.
for example i remember the fork of GCC and how it affected its development processes. unlike GCC i doubt that Xlibre will be merged back, but it has an influence on Xorg nonetheless. what are your thoughts?
pvg•5mo ago
em-bee•5mo ago
unlike GCC, X11 is on the way to obsolescence. and so one question is if there is even a point to continued development. but i also have the sense that Xorg devs would want to prevent Xlibre from growing. and the only way to counteract that is increased activity to show that Xorg is still under active maintenance, because the calls to replace Xorg with Xlibre are already coming, not just from those involved in Xibre but from others who are unaware of the drama and just see that Xlibre is actively maintained while Xorg isn't anymore (in their eyes).
bitwize•5mo ago
em-bee•5mo ago
bitwize•5mo ago
theandrewbailey•5mo ago
em-bee•5mo ago
the ideal outcome would be for Xlibre to become a testing ground for new ideas, where the good ones make it back into Xorg. but the planned obsolescence creates a conflict of interest for Xorg developers, and i suspect that new features will only be accepted reluctantly just to prevent Xlibre from gaining ground.
however, there is another potential outcome, in that the development of wayland focuses more on solving problems that prevent people from switching to it. now that would be a real win.