←back to thread

Xmonad seeking help for Wayland port (2023)

(xmonad.org)
84 points clircle | 1 comments | 18 Sep 25 00:04 UTC | HN request time: 0.202s | source
Show context
jmclnx ◴[19 Sep 25 23:38 UTC] No.45308107[source]▶
That is the thing with Wayland, it is much harder to create a window manager for Wayland. IIRC, fvwm decided not to create a Wayland version due to the difficulty.

When Wayland replacing X, lots of cool window managers and mini applications will be gone.

replies(10): >>45308167 #>>45308326 #>>45308396 #>>45308402 #>>45308487 #>>45308584 #>>45309873 #>>45310118 #>>45311190 #>>45311240 #
charcircuit ◴[20 Sep 25 00:16 UTC] No.45308396[source]▶
This isn't wayland's fault. It's the compositor implementing wayland's fault for not exposing a window manager API. Nothing about wayland prohibits the creation of a window manager API.
replies(4): >>45308435 #>>45308784 #>>45309845 #>>45311041 #
chongli ◴[20 Sep 25 00:21 UTC] No.45308435[source]▶
I’ve heard the same thing about Wayland and NVidia’s drivers. To me, it seems like Wayland was designed to push all the hard work onto everybody else. That way Wayland never gets blamed for anything!
replies(1): >>45308795 #
charcircuit ◴[20 Sep 25 01:09 UTC] No.45308795[source]▶
Not having a defacto compositor was a major blunder and resulted in an enormous delay to the project, reputational damage, and numerous challenges for app developers.
replies(2): >>45309303 #>>45309861 #
hollerith ◴[20 Sep 25 02:58 UTC] No.45309861[source]▶
Do you mean default compositor?
replies(2): >>45310204 #>>45311007 #
1. c-hendricks ◴[20 Sep 25 03:55 UTC] No.45310204[source]▶
I think they meant like a reference implementation, wlroots came a decade into Wayland