Linux

10789 readers

1010 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 1 day 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 36 points 1 day 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 2 points 18 hours ago (2 children)

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

[–] vivendi@programming.dev 5 points 14 hours 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.

[–] MonkderVierte@lemmy.zip 1 points 14 hours ago* (last edited 13 hours ago) (1 children)

but they all work together

Lol, no. Wlroots stuff doesn't work on Sway and vice versa, then there's a few extra limited-scope imlementations with the same problem and Weston is reference only.

And TCP doens't need to duplicate keyboard/mouse input and it builds on UDP to handle low-level stuff. SSH is a better example.

[–] alfredon996@feddit.it 3 points 13 hours ago (1 children)

Lol, no. Wlroots stuff doesn’t work on Sway and vice versa, then there’s a few extra limited-scope imlementations with the same problem and Weston is reference only.

Sway is based on Wlroots. No way Wlroots stuff doesn't work on Sway.

[–] MonkderVierte@lemmy.zip 1 points 13 hours ago* (last edited 13 hours ago) (1 children)

Ah, yup, i mixed them up. Is it 3 years already?
My point is: as it is, wayland will turn out to have one implementation (because the whole bunch of tasks it handles is complex and there's no compositor-to-app compatibility) and everyone will require that. Or basically a X12.

Edit: nope, it was taskbars/docks that really didn't work on both. Do they now?

[–] alfredon996@feddit.it 2 points 13 hours ago

I think there will be more collaboration regarding protocols between Gnome, KDE and Sway, but one single implementation? Hardly.

[–] brian@programming.dev 3 points 16 hours ago

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

[–] badmin@lemmy.today -1 points 16 hours ago* (last edited 16 hours ago)

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.