Conversation
Notices
-
Embed this notice
Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 12-Sep-2024 11:27:16 JST Haelwenn /элвэн/ :triskell: @navi @Catnip Meanwhile each X11 Desktop Environment has their own X11 compositor code as proper compositing isn't part of XOrg. - Doughnut Lollipop 【記録係】:blobfoxgooglymlem: likes this.
-
Embed this notice
anna (navi@social.vlhl.dev)'s status on Thursday, 12-Sep-2024 11:27:18 JST anna @Catnip
> That means every window manager has to have its own Wayland server and compositor code, likely copy pasted for added updating pain.
most compositors write and/or use libraries which can just be updated like any other library
wlroots make tiny and simple wayland setups possible, look at tinywl and dwl -
Embed this notice
catnip@meow.lgbt's status on Thursday, 12-Sep-2024 11:27:21 JST Catnip You don't even really have a simple Wayland server since they fused the window manager to it. That means every window manager has to have its own Wayland server and compositor code, likely copy pasted for added updating pain.
If you want to change your titlebars, you need to get a non-gnome (or install a workaround), replacement for your program, change your entire Wayland server, and then maybe you'll have the ability to configure it (you just lost copy-pasting on a separate program btw). -
Embed this notice
catnip@meow.lgbt's status on Thursday, 12-Sep-2024 11:27:22 JST Catnip The more I learn about Wayland the more I think its a step back from Xorg. The main argument for it is that it has fewer features, making it easier to maintain. However, most if not all of those features where needed.
The result is features being reimplemented in multiple ways, with compatibility issues, and sometimes just being borked or not implemented (_cough_ screenreaders).