Live data from Hacker News

Dwl: Dwm for Wayland

codeberg.org

1–10 of 87 posts

Re: Dwl: Dwm for Wayland

#5
post #2

I wonder if it was considered to submit this as a dwm patch instead.

An X window manager and a Wayland compositor are so radically different beasts that it would probably require a monumental refactor of DWM to make it capable of having an X back-end and a wlroots back-end. Probably easier to just re-create DWM's interface on top of wlroots, like what Sway did with i3.

Also, DWM has an explicit goal of being minimal and to not grow too big. There's no way in hell that Suckless would accept a patch which makes the code way more complex and over 2x larger to make DWM work as a Wayland compositor.

Re: Dwl: Dwm for Wayland

#6
post #5
post #2

I wonder if it was considered to submit this as a dwm patch instead.

An X window manager and a Wayland compositor are so radically different beasts that it would probably require a monumental refactor of DWM to make it capable of having an X back-end and a wlroots back-end. Probably easier to just re-create DWM's interface on top of wlroots, like what Sway did with i3. Also, DWM has an explicit goal of being minimal and to not grow too big. There's no way in hell that Suckless would a…

Suspect you're right, from Acknowledgements:

    dwl began by extending the TinyWL example provided (CC0) by the sway/wlroots developers. This was made possible in many cases by looking at how sway accomplished something, then trying to do the same in as suckless a way as possible.

Re: Dwl: Dwm for Wayland

#7
post #2

I wonder if it was considered to submit this as a dwm patch instead.

i think fork was the correct approach -- it was written in such a way that many of the popular dwm patches can be applied cleanly to dwl.

(i used dwl for quite a while. strong recommend.)

Post reply on HN