I used to be a huge Manjaro fan. There were many ways it let me down, some of which were just bad governance.
The biggest problem though is the AUR. Manjaro uses packages that are older than Arch. The AUR assumes the Arch packages. This, if your use the AUR with Manjaro, your system will break.
It is not a question of if Manjaro will break but when. Every ex-Manjaro user has the same story.
For me, EndeavourOS is everything that Manjaro should be.
If you are a Linux user and like commercial games, you probably would prefer them to work on Linux.
“Market share” on Linux aligns the vested interest of game makers and Linux game players. If the company thinks it can make money, it will do more to allow games to run, or at least do less to stop them.
People are completely missing the point here. “Who made Red Hat the arbiter of when Xorg should end?”
I would say nobody but perhaps a better answer is all of us that have left the work of maintaining Xorg to Red Hat. All that Red Hat is deciding is when they are going to stop contributing. So little is done by others that, if Red Hat stops, Xorg is effectively done.
Others are of course free to step up. In fact, it may not be much work. Red Hat will still be doing most of the work as they will still be supporting Xwayland ( mostly the same code as Xorg ), libdrm, libinput, KMS, and other stuff that both Xorg and Wayland share. They just won’t be bundling it up, testing it, and releasing it as Xorg anymore.
I realize that the major point of GIMP 3 is the port to GTK3. That said, I feel like colour spaces are what people have been waiting for and probably the most significant deficiency that keeps GIMP from being treated as a professional tool.
If they are really this close, why not set the GIMP 3 release date for when colour management is ready?
Non-destructive editing will be huge as well. GIMP 3 is really going to be a crazy leap forward. It is going to be amazing to finally get access to all this work that has been walled off for decades.
The bug situation sounds terrible. Honestly though, they should just get 3 out and then make bug fixing the number one job until it gets into better shape.
Not only is it a small team but right now there are basically two different projects ( 2 and 3 ). With only one code base, perhaps the pace of progress can improve.
I am not saying “This is the Year of the Linux Desktop”. That said, things languished below 2% for decades and now it has doubled in just over a year. With the state of Linux Gaming, I could see that happening again.
Also, if ChromeOS continues to converge, you could consider it a Linux distro at some point and it also has about 4% share.
Linux could exceed 10% share this year and be a clear second after Windows.
That leaves me wondering, what percentage do we have to hit before it really is “The Year of the Linux Desktop”. I have never had to wonder that before ( I mean, it obviously was not 3% ). Having to ask is a milestone in itself.
Calamares uses the QML / Qt toolkit. Most of the people involved in Calamares are also involved in the KDE Project.
XFCE use the GTK toolkit.
So, it is totally reasonable to say that KDE is “more native”.
While Wayland maybe a factor, KDE itself will not be fully Wayland compatible until Plasma 6 next year. So that does not really explain the timing of this move.
I use XFCE myself so I am a bit nervous about the change. We will see.
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.
Manjaro - used to love it. Now the only distro I actively advise against
Garuda - just too much ( I prefer Arch / EndeavourOS )
Elementary - wanted to love it - just too limited
Gentoo - realized I just don’t want to build everything
RHEL Workstation - everything too old
Bhodi - honestly do not remember - long ago
Ubuntu - ok, let’s expand…
These days, I dislike Snaps. Ubuntu just never hit the sweet spot for me though. I was already an experienced Linux user when it appeared and preferred RPM based distros at the tome. Ubuntu always seemed slow and fragile to me. Setting things up, like Apache with Mono back in the day, was “different” on Ubuntu and that annoyed me. For most of its history, it is what I would recommend to new users but I just never liked it myself.
Debian Stable - ok, let’s expand
I really like Debian. It was also a little “alien” when I was using Fedora / Mandrake and the like but it never bothered me like Ubuntu. I ran RHEL / Centos as servers so I did not need Debian stability. As a desktop, Debian packages were always just a little too old ( especially for dev ). The lack of non-free firmware made it a pain.
These days though, Debian has been growing on me. The move to include non-free firmware has made it much more practical. With Flatpaks and Distrobox, aging packages is much less of a problem too. I could see myself using Debian. I am strongly considering moving to VanillaOS ( immutable Debian ).
I basically do not run any RHEL servers anymore. At home, I have a fair bit running Debian already ( Proxmox, PiHole, PiVPN, and a Minecraft server ).
EndeavourOS is my primary desktop these days ( and I love it ) but it is mostly for the AUR. A Debian base with an Arch Distrobox might be perfect. Void seems quite nice as well.
I have been an Open Source advocate forever ( and used to say Free Software and FLOSS ). I have used Linux daily since the 0.99 kernels and I even installed 386BSD back in the day. Despite that, the biggest “not for me” distros right now are anything too closely associated with the politics of the GNU project. It has almost made me want to leave Linux and I have considered moving to FreeBSD. I would love to use Haiku. OCI containers and the huge software ecosystem keep me on Linux though.
The distribution that intrigues me the most right now is Chimera Linux. I run it with an Arch distrobox and it may become my daily driver. The pragmatism of projects like SerenityOS really attracts me. Who knows it may be what finally pulls me away after 30+ years of Linux.
This actually makes it sound like Xorg will be supported longer than I thought.
I understood RHEL9 to already be Wayland based and so I was expecting the clock to runout on Xorg when RHEL8 went off support. RHEL9 does default to Wayland but it sounds like Xorg remained a fully supported option for those that wanted it. The move to Wayland only being proposed for RHEL10 did not happen on RHEL9.
RHEL8 goes off support in 2029 but RHEL9 is supported until 2032. The implications of this article are that Red Hat will not put much energy into Xorg after 2025 ( RHEL10 ) but they will still have to support their customers. This at least means security fixes but it likely means continued viability of modern hardware to a certain extent as well.
Regardless, this also highlights one of the “hidden”‘contributions of Red Hat and how much the entire ecosystem relies on them. This can be seen as good or bad but I wish the public debate involving them would at least accurately reflect it.
I thought this was an article talking about how Wayland makes it possible to perform deeply low-level optimizations to improve the performance of things like high-resolution video playback. Thank you for clearing it up for me.
Most of the GTK environments seem to be doing fine. Most of them seem headed to Wayland as well with the maturity of GTK in Wayland making that easier. Cinnamon will be ready for Wayland in a few months with both XFCE and MATE likely to have something out next year.
Incredibly, GIMP itself may finally get off GTK+ 2. They claim that GIMP 3 will launch in February. We will see how long it takes to get to GTK4. I think the transition will be easier. The jump from 2 to 3 was a big one.
COSMIC of course is going its own way with the Iced toolkit.
On the app side, GTK seems to still be a very popular option.
In terms of conclusions, I do not see mainstream resistance to new GTK versions. Some people balked at GNOME 3 but GNOME today seems more popular than ever. MATE faithfully kept the old GNOME experience but has migrated to newer GTK. It was not a rebellion against the toolkit.
Many people have predicted the death of the small, independent window manager with the coming of Wayland. I have heard multiple times that only large projects like GNOME and KDE would be able to take on the burden of making a compositor.
Now, I do think that lots of no longer actively developed window managers could get left behind. But the idea that it will be too complicated to create a window manager now is turning out to be wrong.
First, fewer desktop environments are getting left behind than feared. XFCE, Cinnamon, and MATE all seem to have Wayland plans now.
The big change is the appearance of not one but multiple compositor libraries designed to make it easier to create a window manager for Wayland. Some of them look like they might make it easier than it was under X. The approach taken by this one makes the idea of hacking around with it very inviting.
Although having to create a compositor has made things difficultly until now, I think the idea of decoupling the compositor for Wayland is going to look smart in the long run.
Being separate from Wayland, compositor devs are free to experiment and window manager authors can select the one that best maps to their goals.
I was reading up on Oasis Linux yesterday. It comes with a Wayland compositor ( SWC ) and tiling window manager ( Velox ) that are less than 20,000 lines of code combined!
It would not be practical for a light-weight distro to trim down Xorg like that. But I the compositor is separate, it can be either smaller or feature rich. SWC is XWayland compatible but obviously that is going to add more size if you need it.
Looking forward to the window manager innovation that projects like Louvre enable.