Obviously reverts happen, in everything. That doesn't mean there aren't developers who are bad, who make untested commits which obviously and immediately break things, and need reverting more than usual.
If you want to defend XLibre, then show us that the number of reverts is standard, or (better!) that the reverts are for subtle issues (like the futex one you linked, it required a significant amount of benchmarking to find!), and isn't just that the code never worked at all.
Saying "Oh, but things get reverted in other systems" means nothing at all, and it's what you spend most of the time talking about.
bitwize · 1d ago
> One would be tempted to say that perhaps they have a vested interest in making it seem like Xorg can not be fixed, even though this patch was merged in 2022, normal users still cannot use this feature in 2025.
This has passed into the "yes, it's happening, and here's why it's a good thing" phase of conspiracy-theory damage control:
The Xorg developers do not want to maintain the legacy X codebase. They do not want to perpetuate the legacy X architecture. If withholding features is what finally gets people to suck it up and switch to Wayland, if it gets app and toolkit developers and fucking NVIDIA to drop their X codepaths and put all their development effort behind Wayland, that's what they will do.
Apple, Microsoft, and Google do this all the time. They drop support for the old and busted and put all their effort into the new hotness. By and large, their user bases do not complain. Only Linux users are autistic enough to go "but muh 40-year-old 'network transparent' [lol, not really, watch the Daniel Stone talk again please] display server written for 8bpp framebuffers long before modern fucking GPUs emerged".
As for Xlibre... to give you an idea of how clownshoes the development community is on that thing...
Not to mention being a Nazi bar. People are starting to wake up and realize what a security risk Nazi- and far-right-authored code is. Alpine already has a security exclusion on it for that reason. Other distros will follow suit.
Obviously reverts happen, in everything. That doesn't mean there aren't developers who are bad, who make untested commits which obviously and immediately break things, and need reverting more than usual.
If you want to defend XLibre, then show us that the number of reverts is standard, or (better!) that the reverts are for subtle issues (like the futex one you linked, it required a significant amount of benchmarking to find!), and isn't just that the code never worked at all.
Saying "Oh, but things get reverted in other systems" means nothing at all, and it's what you spend most of the time talking about.
This has passed into the "yes, it's happening, and here's why it's a good thing" phase of conspiracy-theory damage control:
https://mastodon.social/@alatiera/114661446785833161
The Xorg developers do not want to maintain the legacy X codebase. They do not want to perpetuate the legacy X architecture. If withholding features is what finally gets people to suck it up and switch to Wayland, if it gets app and toolkit developers and fucking NVIDIA to drop their X codepaths and put all their development effort behind Wayland, that's what they will do.
Apple, Microsoft, and Google do this all the time. They drop support for the old and busted and put all their effort into the new hotness. By and large, their user bases do not complain. Only Linux users are autistic enough to go "but muh 40-year-old 'network transparent' [lol, not really, watch the Daniel Stone talk again please] display server written for 8bpp framebuffers long before modern fucking GPUs emerged".
As for Xlibre... to give you an idea of how clownshoes the development community is on that thing...
https://github.com/X11Libre/xserver/pull/56
Not to mention being a Nazi bar. People are starting to wake up and realize what a security risk Nazi- and far-right-authored code is. Alpine already has a security exclusion on it for that reason. Other distros will follow suit.