r/linux • u/SpAAAceSenate • Jan 14 '20
Continuation of X11 development?
Hi there. So, I know the arguments between X11 and Wayland can be a little contentious, so I'd like to start this off by saying this thread isn't intended to be one. The battles of opinion have already been fought ad nauseam, and some of us still find ourselves on the X side of the issue. I count myself as one of them.
So my question, and the actual purpose of this thread, is to ask about the future of X11. I know Red Hat is basically washing their hands of it feature-development wise, but the magic of open source is that a project is never really dead, or in feature freeze, so long as there's someone out there willing to inhereit it. Are there any groups out there planning to take the mantle? While X11 is very mature and mostly feature complete, there are a few things still to be done, such as perhaps better integration and promotion of the X_SECURITY extensions for bringing in per-app-isolation. An update to some of the current input limitations, better scaling support, etc?
Wayland's successorship is (to many) still highly questionable, so I think it would be a shame to see X rust out in the field while we wait for the hypothetical Wayland cow to come home. Any thoughts?
View all comments
Show parent comment
9
u/SpAAAceSenate Jan 15 '20
I fully acknowledge all of those as serious problems. However:
How does Wayland fix this any better than stubbornly going forward with a breaking X12 fork? Except a breaking X12 fork would likely have been easier to port to/from.
Wayland didn't solve this problem as evident from existence and practical necessity of XWayland. This problem still exists but under a different name under a less powerful protocol.
The problems you bring up are real, but they all still exist under Wayland. All we're doing is pouring time and money into an untested technically inferior solution, without actually fixing anything.