It sounded quite bad until I took the time to visit the website and read the entire text:
Xlibre is a fork of the Xorg Xserver with lots of code cleanups and enhanced functionality.
This fork was necessary since toxic elements within Xorg projects, moles from BigTech, are boycotting any substantial work on Xorg, in order to destroy the project, to eliminate competition of their own products. Classic “embrace, extend, extinguish” tactics.
Right after journalists first began covering the planned fork Xlibre, on June 6th 2025, Redhat employees started a purge on the Xlibre founder’s GitLab account on freedesktop.org: deleted the git repo, tickets, merge requests, etc, and so fired the shot that the whole world heard.
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.
It doesn’t matter which country you’re coming from, your political views, your race, your sex, your age, your food menu, whether you wear boots or heels, whether you’re furry or fairy, Conan or McKay, comic character, a small furry creature from Alpha Centauri, or just a boring average person. Anybody who’s interested in bringing X forward is welcome.
Together we’ll make X great again!
It seems to me this person is a bit of a conspiracy theorist and simply has a different understanding of what DEI means.
Maybe an important lesson is not to believe everything you read on the internet.
Keep angrily gaslighting. Surely you’ll EVENTUALLY shame veterans who have been using Linux productively for decades into joining the cult of security over function.
You come into MY home, into MY workflow, take features away from me that have been there ignoring all protests, then have the sheer unmitigated GALL to mock me when I dare to complain?
I WILL continue to use Xorg. My workflow requires it. If that means I have to use an unmaintained window manager forever, so be it.
None of this would be an issue if the Wayland developers weren’t so pigheaded that they insist upon forcing their pure, untainted design philosophy onto the project rather than building an inclusive model that allows for backwards compatibility with the system it’s meant to replace.
I will concede that not every obscure feature has been kept but the vast majority of users are now better served by wayland compositors. I have no idea what you mean by “project”, but if they had no concerns for backwards compatibility, then XWayland wouldn’t exist.
Stopping work on X11 because it’s been an unmaintainable mess for ages doesn’t really count as “forcing” anything upon anyone. I won’t pretend that Wayland protocol development hasn’t seen plenty of disagreements, but it is still a collaborative process.
Your disagreements seem fairly vague to me and I can’t help but think that the “pigheaded” label is somewhat ironic, after your first paragraph.
I am not better served. I am now in the quite new position where I’d have to rewrite some of my own personal software if i simply just decided to change DE
see that’s the problem. Everyone’s first response is that it’s a niche problem. For every complaint. So what? It’s a new problem is the point, however niche.
Btw, this is not a niche problem. Some big projects have explicitly said they have had this very problem
I gladly accept the fossil label, but there’s no contrarian sentiment behind it … I just never felt any pain staying with X11.
Also, the window manager I use is developed by a friend who lives 10min away and texts me every time he has an update, and I love it … doesn’t work on Wayland, though …
Did you try it that with Gnome? I heard that some input methods suffered with the wayland transition because mutter makes some weird choices. From my personal experience, libinput works great with a wacom tablet, so I’m assuming you ran into an issue with a specific DE.
Linux gives users the freedom to keep using x11 :p
They are even free to thanklessly maintain X11 for all the other contrarian fossils, because the developers sure aren’t doing it anymore.
There’s nothing contrarian in using software that works and and fulfills all your needs.
To be fair… XLibre is doing that.
Quote from their readme:
I’ll pass.
It sounded quite bad until I took the time to visit the website and read the entire text:
It seems to me this person is a bit of a conspiracy theorist and simply has a different understanding of what DEI means. Maybe an important lesson is not to believe everything you read on the internet.
Likewise, but claiming no-one has forked Xorg is dishonest, IMO.
deleted by creator
Keep angrily gaslighting. Surely you’ll EVENTUALLY shame veterans who have been using Linux productively for decades into joining the cult of security over function.
You come into MY home, into MY workflow, take features away from me that have been there ignoring all protests, then have the sheer unmitigated GALL to mock me when I dare to complain?
Dude, I am using Linux since 25 years.
Just because you like it so much does not mean that anybody will maintain Xorg for you. Feel free to do it yourself.
I chose Wayland. Not because security, but because I have a primary HDR ultrawide and an old secondary monitor.
Running variable refreshrate does not work with this configuration on Xorg.
HDR does not exist in Xorg.
And never will be.
Just keep in complaining just because someone points out that Xorg is dead.
Xorg is dead! That is not gaslighting, this is a fact
I WILL continue to use Xorg. My workflow requires it. If that means I have to use an unmaintained window manager forever, so be it.
None of this would be an issue if the Wayland developers weren’t so pigheaded that they insist upon forcing their pure, untainted design philosophy onto the project rather than building an inclusive model that allows for backwards compatibility with the system it’s meant to replace.
deleted by creator
I will concede that not every obscure feature has been kept but the vast majority of users are now better served by wayland compositors. I have no idea what you mean by “project”, but if they had no concerns for backwards compatibility, then XWayland wouldn’t exist.
Stopping work on X11 because it’s been an unmaintainable mess for ages doesn’t really count as “forcing” anything upon anyone. I won’t pretend that Wayland protocol development hasn’t seen plenty of disagreements, but it is still a collaborative process.
Your disagreements seem fairly vague to me and I can’t help but think that the “pigheaded” label is somewhat ironic, after your first paragraph.
I am not better served. I am now in the quite new position where I’d have to rewrite some of my own personal software if i simply just decided to change DE
That sounds like a fairly niche problem to have.
see that’s the problem. Everyone’s first response is that it’s a niche problem. For every complaint. So what? It’s a new problem is the point, however niche.
Btw, this is not a niche problem. Some big projects have explicitly said they have had this very problem
I gladly accept the fossil label, but there’s no contrarian sentiment behind it … I just never felt any pain staying with X11.
Also, the window manager I use is developed by a friend who lives 10min away and texts me every time he has an update, and I love it … doesn’t work on Wayland, though …
Wayland doesn’t work for me, I rely on a tablet in lieu of a mouse and under Wayland it’s unusable. I tried hard
Under an X session it behaves flawlessly
Did you try it that with Gnome? I heard that some input methods suffered with the wayland transition because mutter makes some weird choices. From my personal experience, libinput works great with a wacom tablet, so I’m assuming you ran into an issue with a specific DE.
Indeed it works almost flawlessly with Gnome. I am keeping this for now thanks