Linux

10788 readers

1050 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

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

Phoenix: A modern X server written from scratch in Zig (git.dec05eba.com)

submitted 3 days ago by King@sh.itjust.works to c/linux@programming.dev

27 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] UnfortunateShort@lemmy.world 38 points 3 days ago (3 children)

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

[–] MonkderVierte@lemmy.zip 3 points 2 days ago (2 children)

Some people see no benefit in every compositor has to reimplement everything from scratch model Wayland does.

[–] vivendi@programming.dev 6 points 2 days ago (1 children)

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.

[–] brian@programming.dev 3 points 2 days ago

are there not just 2 main libraries or so that all the compositions implement it via?

[–] badmin@lemmy.today -1 points 2 days ago* (last edited 2 days ago) (1 children)

Give me a compositor with at least some of the capabilities of Awesome, AND the ability to apply custom shaders to windows like picom does, 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.

[–] UnfortunateShort@lemmy.world 1 points 1 hour ago

Give me a compositor with at least some of the capabilities of Awesome

KDE Plasma.

and some none alpha-quality VNC solutions

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.