63
Phoenix: A modern X server written from scratch in Zig
(git.dec05eba.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 25 Dec 2025
63 points (90.9% liked)
Linux
12320 readers
382 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
I don't get why people cling to X so desperately. You get no benefits and downsides on top. Wayland is becoming the default for all major and even some smaller DEs, so good luck avoiding all of them and backporting features so Wayland native apps don't break.
I'm not saying you shouldn't do stuff like this for fun. You can do anything for fun. I don't get why of all things you would do that for fun, but go ahead
Some people see no benefit in every compositor has to reimplement everything from scratch model Wayland does.
That's complete horseshit. There are lile 3 major implementations of Wayland and 2 exist because the other one wasn't ready at the time. There are other hobby implementations, but they all work together. Just like how different network stacks can all talk TCP to each other and be fine. Nobody calls TCP fragmented because there are different network stacks...
There are also smaller projects.
Also, the model of a protocol allows Wayland to be deployed on truly exotic operating systems. As long as the top level is compliant, shit just works.
Sway is based on Wlroots. No way Wlroots stuff doesn't work on Sway.
I think there will be more collaboration regarding protocols between Gnome, KDE and Sway, but one single implementation? Hardly.
are there not just 2 main libraries or so that all the compositions implement it via?
Give me a compositor with at least some of the capabilities of Awesome, AND the ability to apply custom shaders to windows like
picomdoes, and some none alpha-quality VNC solutions, then I make seriously consider a permanent move.So it's going to be X11 for at least 2-3 years to come for me. And this is based purely on practical and workflow reasoning. It's is also a logical, technical, and fully informed choice, unlike the entirety of your comment.
KDE Plasma.
The one from KDE.
And before you call me uninformed, please explain to me why per-window custom shaders are a necessity (i.e. overwhelmingly useful and irreplacable) for anyone. And furthermore, what anything you said has to do with me questioning the necessity of not maintaining, but reimplementing X.
I never said anything about Awesome or any X WM, I didn't even say anything about people sticking with an X environment. I commented on a post about a new X implementation, because I wondered why people go out of their way to keep X around, after its own maintainers declared it abandonware.
Old computers can't handle Wayland.
I am running Wayland on an IVB GT1. Your hardware is not possibly shittier than this AND capable of handling modern tasks. Also wayland just needs the infrastructure of doing accelerated draws which if your GPU doesn't support then it won't work with X anyway unless you're running truly exotic 2D accelerators from the 90s
My 2014 Chromebook can run sway just fine. Wayland can be lighter than x
You have no idea how old computers can be, I believe.
You have no idea how light Wayland can be.
I installed Debian on a 2009 Toshiba netbook recently with an Intel Atom N280, KDE worked about the same (not well) in both the X and Wayland modes.
Because of resources, or because of compatibility?