Hooray! A new release of Xorg is always a good reason to celebrate. Long live the all-singing all-dancing feature-rich network-transparent display system which is still the best (and often only) solution for a lot of common user needs, even 39 years after its creation.
Redhat stands to lose their defacto control over X after the XLibre fork so they have to stop trying to kill it. Who would have thought that competition would make things better for everyone?
That's a new take: Project with new release 1 day ago declared deprecated!
I've been using Linux for around 2 decades. I am currently running Fedora 43/KDE Plasma ... and wait for it ... Xorg.
Why? Because it works. It works well!
Why don't I use Wayland? Because it breaks everything.
- Screensharing is just wonky and inconsistent across applications. It has gotten better in the last 2 years, but it's still quite wonky. And janky. And flobby. I **could** put effort into fixing this, but it already works in Xorg.
- I have a bunch of Xorg/xdotool scripts bound to hotkeys. Move, resize windows. If AppX is running and the window isn't shown, show it; otherwise, hide it. If AppX and AppY are both running and meta+y is pressed, then tile in a specific way, else do something different. These scripts are either ungodly difficult to rewrite to work in Wayland or just flat-out impossible in the name of "security".
- Easystroke. https://github.com/mmh0000/easystroke . Nothing like that exists on Wayland (that actually works). And I can not live without it after having it for 20 years.
> An XQuartz installation consists of many individual pieces of software which have various licenses. The X.Org software components’ licenses are discussed on the X.Org Foundation Licenses page.[1] The quartz-wm[2] window manager included with the XQuartz distribution uses the Apple Public Source License Version 2.[3]
Xorg isn't neglected for "ideological reasons", it's neglected because development is work - and most of the people with knowledge of the problem domain decided they didn't want to work on Xorg anymore, and most of the companies that were paying for it decided they didn't want to pay for it anymore (apart from baseline maintenance, Xwayland and security fixes). And the people who want Xorg support maintained in perpetuity rarely seem interested in maintaining Xorg themselves, at least not properly (see this history of Xlibre introducing bugs and LLM slop).
You are free to spend your own time and resources doing the work, but you don't get to dictate how other people spend theirs.
Exactly. Just think about how much work it was to move from X to Wayland, how Nvidia didn't want to play ball, how different the architectures are, in a world where ossification is very much a thing. AND STILL there was enough momentum to get all the major players on board. I have never done any X programming but it must have been bad when people would so readily jump ship and put all that work in. Same for systemd.
Wayland was simpler because it was just a compositor. It meant people interested in graphics acceleration could focus on just that, iterating faster without the friction of the rest of the stack. But now that the Wayland ecosystem has to reinvent everything else, it's clearly at least as much work, if not more so. The initial switch moved the tightly knit rendering developers to a better local optimum, at the expense of a worse global optimum.
Modesetting work was done in 2022, but for some reason no one had released a new stable release of the Xserver with this patch included since then. This was one of the reasons Xlibre was created, there was all these improvements to Xorg sitting ready for release but never being released.
I don't care about either X, but that guy's name is in this release, and judging purely by the number of commits (since I lack X expertise to judge any other way), he seems to be the top contributor.
Looks like there's no way you can avoid "conspiracy theorists" if you want to use X, including Xwayland, eh?
People have all kind of opinions about xlibre as a project and the politics around it that I'm not interested in, but if they're driving xorg to improve, that's a good thing.
I'm not some anti-wayland zealot but you will pry xfce out of my cold dead hands.
>I'm not some anti-wayland zealot but you will pry xfce out of my cold dead hands.
Hard same. I'm using xfce on my laptop with mint xfce edition, and it's a breath of fresh air. Everything just works how you'd expect it to work, and it gets out of your way.
I tried sway a couple years ago and I lost count of the number of things I needed to go and find wayland specific workarounds for. I know things have gotten better since then, but I didn't see any benefit to switching and a whole lot of hassle.
X11 was 21 years old when the Wayland folks decided it was obsolete and needed to be replaced.
Wayland is now about 18 years old. So, by Wayland standards, only 3 more years until it, too, will be obsolete and need to be replaced.
That day can't come soon enough. :D
Maybe the next one will actually be able to do the things I need a display system to do. Until then, at least we've still got X11. And Wayland has taught everyone all sorts of things about what not to do.
Yeah, but they haven't added any features in years, from what I assumed to be a maintenance only/feature frozen stance in favor of Wayland, which is (primarily) why xlibre forked.
With a project as user/dev hostile as wayland, it's much better to be a 'last mover' than first.
For the life of me, I'll never understand how wayland got traction with the community.
'Hey guys, we decided to implement a display server from scratch! We broke a ton of existing functionality and made a ton of low level stuff that X used to handle the responsibility of WM/DE devs!'
You'll excuse me if I am not terribly enthusiastic about breaking all sorts of functionality to solve a security problem I've never experienced in my 25 years on linux.
IMO the issue is that the same group stewarding Wayland was also xorg, and intentionally stifled improvement on xorg even when the work just a matter of merging the PR.
Merging a PR by drive-by contributors is far from trivial. As the maintainer, you become responsible for the other person's code for all eternity; it's on you to read it, understand it, update it when stuff around it changes, and fix it when it breaks.
Not a problem for obviously-correct changes of a couple of lines, but most PRs aren't like that.
I understand and that's a fair point. I should have phrased that differently, in that the PRs for features were waiting to be merged. I'm sure merging into a codebase as... storied? as xorg is no small task.
Open source developers are not required to spend their time prioritizing your priorities. You just have to look to Xlibre to see that a lot of contributions are quite bad quality, and in a C codebase of Xorg's complexity and security profile it's not a small job to review things.
Nothing I said in any way implied that freedesktop should be required to do anything. I can't speak to the quality of xlibre merges, only that if whatever is going on over there led to improvements in xorg after a drought, that's a good thing.
If wayland had been sold as a hardened display for those who needed that level of security, I would not have a problem with it.
As it is, the community got constantly browbeat with 'this is the future' and 'it's so much faster!' when recent benchmarks have proven that to be false.
Then go use X. Nobody's stopping you, you can just ignore any brow beating. /ignore is a useful IRC command.
You'll probably find it to be a not great experience, since almost all the people who spend their time actually working on graphics and GUIs in the Linux world prefer to work on Wayland. So X doesn't get much love these days (and you're not entitled to their efforts after all). But it's not like they erased all the old X code from existence.
Wayland is not a "display server", it's a display protocol.
A lot of the "existing functionality" that it broke has nothing to do with displays, it's stuff that got crammed into Xorg at some point whether it made sense or not.
I find it quite funny that many of the same people that rag on systemd and say it does too many things, are big fans of Xorg doing a bunch of things that "display server" probably should not be handling.
Even if Wayland was a "display server", it would still "remove existing functionality" if it meant that in any principled sense, because "display server" is only half of what Xorg does.
But sure, the transition was difficult and took a long time.
>Wayland is not a "display server", it's a display protocol.
I, as an end user, do NOT care.
>A lot of the "existing functionality" that it broke has nothing to do with displays, it's stuff that got crammed into Xorg at some point whether it made sense or not.
I also don't care about ivory tower ideals of what is within the dominion of 'display' and what is not. The fact of the matter is their changes broke a ton of functionality, and instead of even trying to provide feature parity, they basically dumped all that responsibility onto the WM/DE devs.
I have no idea why the community didn't take one look at their proposal and flatly ignore them.
> instead of even trying to provide feature parity, they basically dumped all that responsibility onto the WM/DE devs.
In other words, the Wayland people should perhaps have defined official protocol extensions early on to cover most of what X did, thus preventing all the initial interop issues when Gnome and KDE and Sway tried to reinvent them independently.
In hindsight, it's my opinion that wayland, if it had to exist at all, should have been implemented like this:
1. Add GBM to graphics drivers and start working it up the stack from the bottom, stopping at Xorg. That is, make rootful XWayland the standard Xorg before standalone even is a thing. This reduces maintenance work up front rather than belatedly.
2.a. Implement weston as a standalone compositor.
2.b. Actually make weston fully functional. Figure out everything needed to provide an actual working desktop environment with the features that users expect out of the box. Standardize all the protocols needed for at least a basic XFCE-ish environment rather than hoping someone else will do it.
3. Then, only after these things are done and working, announce to the world that wayland, a quiet project that has until now explicitly suggested nobody use it, is now the future of linux graphical systems and everyone should plan to migrate.
The community doesn't really have a say because Xorg is effectively on life support and the Xorg devs are now working on Wayland. There aren't many people in this world who could keep Xorg going. Some distros are sticking to Xorg, but it will become more and more difficult in the coming years.
Not in the short-term, for sure, and probably not even in the mid-term. But hardware keeps changing, and at some point nobody will care enough (or be able) to implement proper support for it in X (or proper support of X in that hardware). Hopefully we still have at least a decade of X though.
This pretty much. Xorg got almost everything that I care about to have a functionning GUI. You only startx and the only thing you may need are utils programs like a wm, a compositor, a bar… now you have conflicting implementation from gnome, kde, wlroots,… each with its own set of features.
Yeah, instead of the wayland folks leading the effort to fix issues, it's often some individual DE / WM going off, fixing it the way they prefer, and wayland grudgingly adopting it as official because they know the ecosystem is fragmenting bad enough as it is.
And this transition is nowhere near done. Just look at Kicad and pretty much any DAW that loads audio plugins (to name two major usecases where Wayland simply doesn't cut it).
Sure Xwayland exists and mostly (not entirely) works, but that's a band-aid for what is essentially a "we broke it and don't care" approach.
The daw problem is really really bad too. We've got a de facto standard forming right now where you link libwayland.so and hope the structs never ever ever change in the next 30 years.
> Wayland is not a "display server", it's a display protocol.
This is a huge part of what "user/dev hostile" means in my book; with Wayland, getting a working desktop always someone else's responsibility, all features have to be reimplemented across DEs endlessly (with often-incompatible variations, of course), and they all blame each other and program authors for bugs while the Wayland project refuses to even acknowledge basic features like desktop automation or screen recording.
> But sure, the transition was difficult and took a long time.
And this irks me too, people are convinced they're done but I still don't have xmacro. And flameshot is broken, while the alternatives suck. And support for everything depends on the DE now. And java.awt.Robot is broken with no replacement. And the clipboard randomly misses copies. And OBS screen recording is broken for me. And there's no support for display resolution scaling. And ssh -X is gone, while waypipe doesn't work all programs.
But hey, at least there's HDR now or something! It was definitely worth replacing a functioning stack for this. I'm so glad that Plasma 6.8 removes X support!
> I'll never understand how wayland got traction with the community
There were only a few people willing to work on an alternative, and they didn't have to take a vote, so they just did what they wanted. Corporations and projects adopted it because they wanted something different, and it was the only other option.
Now that we have AI, it will be much easier for genuine community alternatives to emerge, even if we have to battle over the legal ramifications. I for one am willing to go without "official support" to have software that doesn't suck.
Hooray! A new release of Xorg is always a good reason to celebrate. Long live the all-singing all-dancing feature-rich network-transparent display system which is still the best (and often only) solution for a lot of common user needs, even 39 years after its creation.
Well, Quartz is okay too, even though it lacks network transparency.
Arcan is looking like a very promising successor to the X protocol and Xorg server. It's not there yet, but it gets closer year after year.
Note that Enrico Weigelt is the "XLibre" guy and some of his fixes made it into this release, you can search for his name in the message.
This is a much more substantial changelog than I was expecting for something that is often presented as a deprecated project.
Redhat stands to lose their defacto control over X after the XLibre fork so they have to stop trying to kill it. Who would have thought that competition would make things better for everyone?
I doubt they care too much. They probably just have customers with applications stuck on a legacy window system. And they pay for that maintenance.
It basically is a deprecated project.
That's a new take: Project with new release 1 day ago declared deprecated!
I've been using Linux for around 2 decades. I am currently running Fedora 43/KDE Plasma ... and wait for it ... Xorg.
Why? Because it works. It works well!
Why don't I use Wayland? Because it breaks everything.
The mention of XQuartz (for macOS) reminded me to check that, and 2.8.6 was released mid-July:
* https://www.xquartz.org/releases/bare/XQuartz-2.8.6.html
Previously 2.8.5 was out in 2023:
* https://www.xquartz.org/releases/bare/XQuartz-2.8.5.html
There's a XQuartz 2.8.7 beta as well (xorg-server 26.1 rebase):
* https://www.xquartz.org/releases/index.html
omg, it's been over a decade since I have last used XQuartz. Did they finally open source the whole quartz-wm?
> An XQuartz installation consists of many individual pieces of software which have various licenses. The X.Org software components’ licenses are discussed on the X.Org Foundation Licenses page.[1] The quartz-wm[2] window manager included with the XQuartz distribution uses the Apple Public Source License Version 2.[3]
* https://www.xquartz.org/index.html
Just looked it up, that Apple license is indeed approved as open source/free software by the FSF and OSI!
> FSF approved Yes (Version 2.0, not versions 1.0, 1.1 and 1.2)[2][3]
> OSI approved Yes
* https://en.wikipedia.org/wiki/Apple_Public_Source_License
Ah, I can see that the binary blob is not needed anymore. Nice.
Intel modesetting driver with tearfree support in a xorg release!
Hoorah! Hopefully big distros will at least offer an optional upgrade to this.
I'm all for people switching to wayland but there should be choice and xorg should not be neglected for ideological reasons.
Xorg isn't neglected for "ideological reasons", it's neglected because development is work - and most of the people with knowledge of the problem domain decided they didn't want to work on Xorg anymore, and most of the companies that were paying for it decided they didn't want to pay for it anymore (apart from baseline maintenance, Xwayland and security fixes). And the people who want Xorg support maintained in perpetuity rarely seem interested in maintaining Xorg themselves, at least not properly (see this history of Xlibre introducing bugs and LLM slop).
You are free to spend your own time and resources doing the work, but you don't get to dictate how other people spend theirs.
Exactly. Just think about how much work it was to move from X to Wayland, how Nvidia didn't want to play ball, how different the architectures are, in a world where ossification is very much a thing. AND STILL there was enough momentum to get all the major players on board. I have never done any X programming but it must have been bad when people would so readily jump ship and put all that work in. Same for systemd.
Wayland was simpler because it was just a compositor. It meant people interested in graphics acceleration could focus on just that, iterating faster without the friction of the rest of the stack. But now that the Wayland ecosystem has to reinvent everything else, it's clearly at least as much work, if not more so. The initial switch moved the tightly knit rendering developers to a better local optimum, at the expense of a worse global optimum.
Modesetting work was done in 2022, but for some reason no one had released a new stable release of the Xserver with this patch included since then. This was one of the reasons Xlibre was created, there was all these improvements to Xorg sitting ready for release but never being released.
Luckily there is XLibre if the xorg developers can't develop X any more.
If you want to use buggy software maintained by a conspiracy theorist because wayland is too woke for you them yeah sure.
I don't care about either X, but that guy's name is in this release, and judging purely by the number of commits (since I lack X expertise to judge any other way), he seems to be the top contributor.
Looks like there's no way you can avoid "conspiracy theorists" if you want to use X, including Xwayland, eh?
It looks like it's under more active development currently, however I don't see them adding many big new features at this point.
Isn't most of this already in xlibre?
People have all kind of opinions about xlibre as a project and the politics around it that I'm not interested in, but if they're driving xorg to improve, that's a good thing.
I'm not some anti-wayland zealot but you will pry xfce out of my cold dead hands.
>I'm not some anti-wayland zealot but you will pry xfce out of my cold dead hands.
Hard same. I'm using xfce on my laptop with mint xfce edition, and it's a breath of fresh air. Everything just works how you'd expect it to work, and it gets out of your way.
I tried sway a couple years ago and I lost count of the number of things I needed to go and find wayland specific workarounds for. I know things have gotten better since then, but I didn't see any benefit to switching and a whole lot of hassle.
X11 was 21 years old when the Wayland folks decided it was obsolete and needed to be replaced.
Wayland is now about 18 years old. So, by Wayland standards, only 3 more years until it, too, will be obsolete and need to be replaced.
That day can't come soon enough. :D
Maybe the next one will actually be able to do the things I need a display system to do. Until then, at least we've still got X11. And Wayland has taught everyone all sorts of things about what not to do.
Xorg has had releases for years and will continue to do so. But as you can see in the announcement, enterprise users are the driving factor.
Yeah, but they haven't added any features in years, from what I assumed to be a maintenance only/feature frozen stance in favor of Wayland, which is (primarily) why xlibre forked.
Even xfce will one day move to Wayland.
They're already busy doing precisely that: https://lwn.net/Articles/1078942
With a project as user/dev hostile as wayland, it's much better to be a 'last mover' than first.
For the life of me, I'll never understand how wayland got traction with the community.
'Hey guys, we decided to implement a display server from scratch! We broke a ton of existing functionality and made a ton of low level stuff that X used to handle the responsibility of WM/DE devs!'
I think it was the "security" argument. Some magic words like "security" and "protect the children" make most people go insane, abandon all reason.
You'll excuse me if I am not terribly enthusiastic about breaking all sorts of functionality to solve a security problem I've never experienced in my 25 years on linux.
Xorg's security (and X11 in general) is objectively terrible - this is not even a debatable question.
Great, so let wayland be a hardened option for those who care.
It is and you're free to use X if you want
IMO the issue is that the same group stewarding Wayland was also xorg, and intentionally stifled improvement on xorg even when the work just a matter of merging the PR.
Merging a PR by drive-by contributors is far from trivial. As the maintainer, you become responsible for the other person's code for all eternity; it's on you to read it, understand it, update it when stuff around it changes, and fix it when it breaks.
Not a problem for obviously-correct changes of a couple of lines, but most PRs aren't like that.
I understand and that's a fair point. I should have phrased that differently, in that the PRs for features were waiting to be merged. I'm sure merging into a codebase as... storied? as xorg is no small task.
>and intentionally stifled improvement on xorg
Open source developers are not required to spend their time prioritizing your priorities. You just have to look to Xlibre to see that a lot of contributions are quite bad quality, and in a C codebase of Xorg's complexity and security profile it's not a small job to review things.
Nothing I said in any way implied that freedesktop should be required to do anything. I can't speak to the quality of xlibre merges, only that if whatever is going on over there led to improvements in xorg after a drought, that's a good thing.
If wayland had been sold as a hardened display for those who needed that level of security, I would not have a problem with it.
As it is, the community got constantly browbeat with 'this is the future' and 'it's so much faster!' when recent benchmarks have proven that to be false.
Then go use X. Nobody's stopping you, you can just ignore any brow beating. /ignore is a useful IRC command.
You'll probably find it to be a not great experience, since almost all the people who spend their time actually working on graphics and GUIs in the Linux world prefer to work on Wayland. So X doesn't get much love these days (and you're not entitled to their efforts after all). But it's not like they erased all the old X code from existence.
> You'll probably find it to be a not great experience
I'm confused where I'm likely to be suffering. If I start using Wayland tomorrow would I even notice? Apart from having to switch DEs, of course.
Are you seriously acting like every application having full access over other applications is not an actual security issue?
Wayland is not a "display server", it's a display protocol.
A lot of the "existing functionality" that it broke has nothing to do with displays, it's stuff that got crammed into Xorg at some point whether it made sense or not.
I find it quite funny that many of the same people that rag on systemd and say it does too many things, are big fans of Xorg doing a bunch of things that "display server" probably should not be handling.
Even if Wayland was a "display server", it would still "remove existing functionality" if it meant that in any principled sense, because "display server" is only half of what Xorg does.
But sure, the transition was difficult and took a long time.
>Wayland is not a "display server", it's a display protocol.
I, as an end user, do NOT care.
>A lot of the "existing functionality" that it broke has nothing to do with displays, it's stuff that got crammed into Xorg at some point whether it made sense or not.
I also don't care about ivory tower ideals of what is within the dominion of 'display' and what is not. The fact of the matter is their changes broke a ton of functionality, and instead of even trying to provide feature parity, they basically dumped all that responsibility onto the WM/DE devs.
I have no idea why the community didn't take one look at their proposal and flatly ignore them.
> instead of even trying to provide feature parity, they basically dumped all that responsibility onto the WM/DE devs.
In other words, the Wayland people should perhaps have defined official protocol extensions early on to cover most of what X did, thus preventing all the initial interop issues when Gnome and KDE and Sway tried to reinvent them independently.
In hindsight, it's my opinion that wayland, if it had to exist at all, should have been implemented like this:
1. Add GBM to graphics drivers and start working it up the stack from the bottom, stopping at Xorg. That is, make rootful XWayland the standard Xorg before standalone even is a thing. This reduces maintenance work up front rather than belatedly.
2.a. Implement weston as a standalone compositor.
2.b. Actually make weston fully functional. Figure out everything needed to provide an actual working desktop environment with the features that users expect out of the box. Standardize all the protocols needed for at least a basic XFCE-ish environment rather than hoping someone else will do it.
3. Then, only after these things are done and working, announce to the world that wayland, a quiet project that has until now explicitly suggested nobody use it, is now the future of linux graphical systems and everyone should plan to migrate.
The community doesn't really have a say because Xorg is effectively on life support and the Xorg devs are now working on Wayland. There aren't many people in this world who could keep Xorg going. Some distros are sticking to Xorg, but it will become more and more difficult in the coming years.
People keep saying Xorg will stop working, but it has yet to turn into a pumpkin, so I dunno man.
Can it do new things? Eh, probably not. Do I need it to do new things? Not really.
Not in the short-term, for sure, and probably not even in the mid-term. But hardware keeps changing, and at some point nobody will care enough (or be able) to implement proper support for it in X (or proper support of X in that hardware). Hopefully we still have at least a decade of X though.
If nothing else this is a very strong commentary on just how challenging landing positive changes in Xorg felt to the community.
This pretty much. Xorg got almost everything that I care about to have a functionning GUI. You only startx and the only thing you may need are utils programs like a wm, a compositor, a bar… now you have conflicting implementation from gnome, kde, wlroots,… each with its own set of features.
Yeah, instead of the wayland folks leading the effort to fix issues, it's often some individual DE / WM going off, fixing it the way they prefer, and wayland grudgingly adopting it as official because they know the ecosystem is fragmenting bad enough as it is.
And this transition is nowhere near done. Just look at Kicad and pretty much any DAW that loads audio plugins (to name two major usecases where Wayland simply doesn't cut it).
Sure Xwayland exists and mostly (not entirely) works, but that's a band-aid for what is essentially a "we broke it and don't care" approach.
The daw problem is really really bad too. We've got a de facto standard forming right now where you link libwayland.so and hope the structs never ever ever change in the next 30 years.
Also, as benchmarks show, xwayland introduces pretty bad latency..
The latency isn't that bad, it's reasonable for a compatibility shim.
> Wayland is not a "display server", it's a display protocol.
This is a huge part of what "user/dev hostile" means in my book; with Wayland, getting a working desktop always someone else's responsibility, all features have to be reimplemented across DEs endlessly (with often-incompatible variations, of course), and they all blame each other and program authors for bugs while the Wayland project refuses to even acknowledge basic features like desktop automation or screen recording.
> But sure, the transition was difficult and took a long time.
And this irks me too, people are convinced they're done but I still don't have xmacro. And flameshot is broken, while the alternatives suck. And support for everything depends on the DE now. And java.awt.Robot is broken with no replacement. And the clipboard randomly misses copies. And OBS screen recording is broken for me. And there's no support for display resolution scaling. And ssh -X is gone, while waypipe doesn't work all programs.
But hey, at least there's HDR now or something! It was definitely worth replacing a functioning stack for this. I'm so glad that Plasma 6.8 removes X support!
> For the life of me, I'll never understand how wayland got traction with the community.
Corporate drive. Originally sponsored by Intel followed by IBM (RedHat) and the rest followed suit.
Money, the "cure" to the hacker ethos.
Sauce?
It's how any of these projects get shifted in distribution if not sponsored.
> Kristian Høgsberg, I work at Intel in the graphics team in the Open Source Technology Center. I'm the founder and maintainer of the Wayland project.
You either pitch or bring it with you. Demonstrate a tech demo and you're granted an engineer or two. It's how Amiga came to be, Steve Jobs with NeXT.
It appears you can no longer link any reddit link now without being asked to login and it appears they've now nuked old.reddit
If you have an account this thread has some very insightful comments. https://www.reddit.com/r/linux/comments/1m0ztn/how_is_waylan...
> I'll never understand how wayland got traction with the community
There were only a few people willing to work on an alternative, and they didn't have to take a vote, so they just did what they wanted. Corporations and projects adopted it because they wanted something different, and it was the only other option.
Now that we have AI, it will be much easier for genuine community alternatives to emerge, even if we have to battle over the legal ramifications. I for one am willing to go without "official support" to have software that doesn't suck.
And I'll be there.
There's already and experimental support no?
> you will pry xfce out of my cold dead hands
AwesomeWM for me. I've essentially fused with it. Warts and all.
Duplicate functionality compared to XLibre was reimplemented here from scratch, or sourced from XLibre?
At least one was looks like it was sourced from XLibre: https://github.com/X11Libre/xserver/pull/1314
Pulling good ideas from downstream forks is actually kind of what open source is all about, isn't it?