News for hackers. Stuff that matters.

A comment on XFCE Wayland Development Roadmap. Parent comment

Re:XFCE Wayland Development Roadmap by nurbl on Thursday September 14, 2023 @08:39AM (#37508132)
I'm running i3 + xfce-settings for many years and to me it's a perfect solution, extremely stable. I have no opinion on wayland, but I dread the day when I'll have to move to it, as it will mean switching WM, and I assume lots of details will change. But at least it seems XFCE should still work! I just want my desktop environment to fade into the background and not bother me. I'm used to all the little quirks now :)
[ Parent | on HN ]
Re:XFCE Wayland Development Roadmap by loudmax on Thursday September 14, 2023 @08:44AM (#37508202)
The `sway` window manager is an attempt to clone i3 for Wayland. If you do have to switch, that part at least, shouldn't be too painful.
[ Parent | on HN ]
Re:XFCE Wayland Development Roadmap by bravetraveler on Thursday September 14, 2023 @08:51AM (#37508286)
"Sway" is i3 with Wayland, fear not (so much)

You would probably have to change your keybindings a little but otherwise it's very similar... before the Wayland part

Switching from i3 to Sway kept 90% of the same config for me, changing only keybinds and output configuration.

I did have to override args/env for some things to truly do Wayland, but that's shortening every day

[ Parent | on HN ]
Re:XFCE Wayland Development Roadmap by vidarh on Thursday September 14, 2023 @09:12AM (#37508537)
I feel much the same, though I'm running bspwm, with my own cobbled together scripts rather XFCE. There's zero upside to me in an upgrade, but I worry it eventually will become hard to avoid.

I'm increasingly tempted to grab a simple Wayland compositor and "bolt on" a minimalist X implementation directly on it to also allow X connections with just enough of the protocol implemented to allow running some simpler X WMs (but I'd love it if someone beat me to it).

For WMs with lots of fancy stuff it'd can take quite a bit of the X API to support, but a simple X WM doesn't typically use that many request types (I just looked at i3's source, and it's X interactions are pretty simple...

[ Parent | on HN ]