this post was submitted on 28 Nov 2023
156 points (98.8% liked)

Linux

48181 readers
1200 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Red Hat has formally confirmed what many were thinking: Red Hat Enterprise Linux 10 will be doing away with X.Org Server support aside from XWayland.

For those making use of the Red Hat Enterprise Linux 10 in a desktop setting, RHEL10 due for release in H1'2025 will be Wayland-focused. X11 client support will only come via XWayland.

This does also further solidify the X.Org Server in effect being dead upstream. Red Hat engineers were typically the ones managing new X.Org Server releases as well as carrying on with various bits of development.

you are viewing a single comment's thread
view the rest of the comments
[–] theshatterstone54@feddit.uk 41 points 11 months ago (1 children)

So X.Org fully dies on the 31st May 2035 with the end of Extended Life Cycle Support for RHEL 9. We have XOrg's death day. Even if it will likely be on it's death bed taking its final breaths for years before that.

[–] LeFantome@programming.dev 18 points 11 months ago (1 children)

I thought this as well but the more I think about it, the less true this seems. From an engineering point of view, it could last longer.

Xwayland is really just Xorg and Xwayland continues to be supported in RHEL10 and beyond.

Xorg and Wayland compositors have grown together in some ways. Both now use libinput, libdrm, and KMS for example. Those are not going away.

Xwayland is really just Xorg adapted to talk to Wayland instead of KMS and libinput. It is mostly the same code. So, Xorg will continue to benefit from the care and attention that Xwayland gets. Perhaps there may not be many new features but the code is not going to bit rot and security will continue to be addressed. While Xwayland does not use libinput or KMS, the Wayland compositor itself will, so those pieces are also going to be maintained including new features and new hardware support. Mesa is a common component as well.

So, while Red Hat may stop coordinating releases of Xorg at some point, a surprising amount of the code will still be actively maintained and current. It may not take a lot of work for somebody else to take over and bundle it up as a release.

What will probably kill Xorg is lack of demand.

Despite the anti-Wayland chatter, the migration to Wayland looks like it will gain substantial momentum this year and next and not only on Linux. Three to five years from now, the number of people that still care about Xorg ( as the primary display server - not as Xwayland ) may be very small indeed. Obviously it will be running on older systems for a long, long time but, ten years from now, installing Xorg on a new system is likely to be very rare ( like CP/M now rare ).

Red Hat may end up being one of the very last players that cares about Xorg after 2030. My guess is that most of the current never-Wayland crowd will have moved to it long before then.

[–] theshatterstone54@feddit.uk 1 points 11 months ago

Yeah, thank you for doing such a good explanation of it. I completely agree. Truth be told, the features I missed with Qtile on Wayland (some bugs that took a while to iron out, and are only fixed in qtile-git, as well as rounded corners, which are a work-in-progress, leaving me with only 1 issue with Qtile, that being how difficult Qtile Wayland is to install and set up, if only there was a working guide for doing so via pip, but pywayland and/or pywlroots via pip are usually broken), were all fixed by Hyprland, so I'm on Hyprland full time now, and I love it! There is only one minor issue I have (drop downs from Waybar's systray are kinda broken on Hyprland, rendering weirdly, with strange black gaps between sections and rendering under, rather than over, windows).