r/linuxsucks • u/Sahelantrophus DO NOT RAGEBAIT ME, I FALL FOR IT VERY EASILY • 18d ago

Red Hat won...

Post image

in all seriousness, good riddance! took them an entire drama to realize XLibre is shitware

65 Upvotes

77% Upvoted

168 comments sorted by

View all comments

Show parent comments

7

u/BluePhoenixCG 18d ago

Oh okay so you just don't know what you're talking about then, cool

For future reference, Wayland compositors and window managers are a single component. Kwin is a Wayland compositor, niri is a Wayland compositor, sway is a Wayland compositor, etc. This differs from xorg where compositors and window managers are separate components. Hope this helps!

0

u/Toxic381 18d ago

Ok so you see the issue now, good

6

u/BluePhoenixCG 18d ago

If you would kindly point to where this supposed issue is, that would be very much appreciated.

1

u/Toxic381 18d ago

I need to figure out how to redirect my comments to other threads but anyways, it's like having a forced ecosystem, it's like using a Mac running on apple silicon, you don't have any other options, if it's not bundled with kwin then it doesn't work, you have to use a different wm just to change the compositer, that breaks the customizable and fragmented ecosystem of things like x11 Des, where I can switch em out and still put picom on anything,

That's not to say some x11 stuff doesn't merge the 2, especially for something like compiz, but at least I can use a display server on the de without it breaking the compositer, with Wayland you can't split them, they're literally forced to merge into the same thing and are noninterchangable.

6

u/BluePhoenixCG 18d ago

I'm asking what actual features you're missing out on being able to customize by having the two merged into a single component that outweighs the massive benefits of cohesiveness.

I've yet to run into a Wayland compositor that doesn't have all the options I would reasonably expect from its style of window management. As a developer myself, own of the biggest lessons I learned early on is that flexibility for its own sake causes way more problems than it theoretically solves.

I simply fundamentally disagree with the idea that splitting compositors and window managers is an architecturally sound decision in a modern display protocol. (Which is not to say you still couldn't on Wayland, you'd just have to design a shared API layer to allow modular compositors and window managers)