Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
According to that article, Xorg hasn't been properly maintained for years. I suppose wayland is the future, like Xorg was the future once. When I started out with Linux, it was Xfree86 and that wasn't being maintained properly either.
The elimination of X will probably force everyone using old hardware to the BSDs, similar to what Microsoft is doing with TPM2. Also I (tinfoil hat on) strongly suspect, Wayland will require systemd in some future release.
So, I believe many Linux hobbyist will move on to a BSD. Why, with Wayland it is very difficult to create custom window managers when compared to X. Plus creating tiny little clients (like xload, xbiff, xeyes, too many to list) is probably a lot harder. Plus the resources will probably be higher. So Linux will then end up as a commercial OS similar to Microsoft Windows, with Microsoft's hands in it.
But OpenBSD has xenodm, which I am hoping all the BSDs will team up to support. Then I will at least have an escape route from an OS controlled by Red Hat and Large Commercial Companies.
Last edited by jmccue; 11-29-2023 at 07:36 AM.
Reason: grammer
I share the concerns about Wayland acquiring a systemd entanglement.
Also, so far Wayland is not properly formed into a viable alternative to X, yet. I suppose that will segue into not being maintained properly either, thus continuing the fine tradition.
Seriously, there are some dangerous shortcomings with X which were written up in detail a great many years ago now. Wayland had potential, and had the advantage of more or less starting as a new project, but after 15 years without major progress (from an end-user perspective), there is a larger problem which needs to be addressed.
You'll always be able to build from scratch, won't you?
Please, say yes. It's my final hope!
I wouldn't put it past Gnome to drop X11 support from GTK itself before too long in order to force the adoption. Either that or apps themselves will start to require Wayland (or worse still, a desktop specific compositor, due to use of some desktop specific protocol extensions).
Regardless of whether X11 can still be built or not, unless you're going to stick with outdated apps you might not have a choice for much longer.
As a fvwm user who likes working in X11, this prospect does not please me at all.
#1 I think that train started down the track about three years ago, it is just not an express.
#2 I expect x.org to be available AS AN OPTION for at least another decade. Support for older hardware is a "Linux thing"!
#3 I will be surprised if Wayland does not come to support multiple older hardware platforms with time. Almost everything else in the FOSS world has.
(I still have one 32-bit i686 platform that runs Linux. Without GUI and slow, but it still works.)
I share the concerns about Wayland acquiring a systemd entanglement.
AFAIK the systemd component that creates the entanglements is always systemd-logind, and that can be replaced by elogind. That's how Slackware, AntiX and Devuan do it. In fact it's what elogind was created for. Like eudev (I believe we owe both of them to the Gentoo team).
That's the Linux way of doing things. If something unpopular gets pushed, some angry hacker will always create an alternative.
Distribution: antiX using herbstluftwm, fluxbox, IceWM and jwm.
Posts: 631
Rep:
Quote:
Originally Posted by hazel
AFAIK the systemd component that creates the entanglements is always systemd-logind, and that can be replaced by elogind. That's how Slackware, AntiX and Devuan do it. In fact it's what elogind was created for. Like eudev (I believe we owe both of them to the Gentoo team).
That's the Linux way of doing things. If something unpopular gets pushed, some angry hacker will always create an alternative.
Actually hazel, antiX does not use elogind at all. We use seatd as a 'replacement' for systemd-logind.
This comment (phoronix.com Comment 39) seems to describe one big issue with Wayland, and it may be the reason nvidia and amd is having issues with it.
As you read other comments, seems some people seem to confirm this. This a a partial quote from the comment:
Quote:
AMD graphics developers. They say that one of the biggest reasons why Linux/FOSS doesn't have feature parity with Windows is literally because of Wayland and the umpteen display managers situation. Features that don't go directly into the driver need to be added to the display manager and, unlike Windows, there is no centralized display manager to work with
This is going to be like when someone does that trick with the table cloth where they yank the cloth out from under the stuff on the table and it's supposed to stay in place but instead everything ends up broken and on the floor.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.