46
Several New X.Org Libraries See 2026 Releases
(www.phoronix.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jan 2026
46 points (96.0% liked)
Linux
12111 readers
264 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
Actually that is not too far off from being true.
mesa right now has this massive regression on wayland: https://gitlab.freedesktop.org/mesa/mesa/-/issues/14674
And not long ago all gtk4 apps were totally broken on intel with wayland, this was recently fixed on mesa but that change has only hit people using archlinux and other rolling release distros.
No, it absolutely is very far off, unless you find actual studies & user feedback. Lets not do weird mental gymnastics to find logic in pure hyperbole. You gotta give me way more than one 1-week-old bug, and one bug that was quickly caught and fixed. Bugs are going to happen in software that is worked on.
The reason X was stable for a long time is because many new & nowadays important features (like fractional scaling) weren't being worked on, the ecosystem was mostly frozen. There's more churn around Wayland because it's newer & supports more (and often structurally much better) approaches to solving its problems. Don't want to get caught in that? Maybe don't use a distro that is specifically known for shipping new software very quickly.
The performance regression? It hasn't been fixed.
You will run into old wayland bugs lol, like GTK4 apps being totally broken on intel.
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38373
On wayland even getting apps to draw their own icons is a total disaster, and doesn't help the constant sabotage from gnome of refusing to fix those issues, and don't get me started on the csd mess which is another source of nightmares.
Wayland suffers a lot of internal fragmentation, we didn't see these kind of issues in the move from pulseaudio to pipewire because there is really only one implemenation of pipewire, guess what would have happened a bunch of DEs decided to make their own implementations of pipewire instead?
You know - when you list two points, and I refer to those two points in my response, maybe assume that I'm responding in the same order you listed?
Nothing was quickly caught and fixed, the bug report is 7 months old:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13319