Why should old WMs/DEs add support for Wayland, why not just write new for Wayland specifically?
XFCE 4.20 aims to bring preliminary Wayland support
11–20 of 204 posts
Re: XFCE 4.20 aims to bring preliminary Wayland support
#12XFCE being stuck on X11 was what finally made me finally move to KDE when I installed Linux on my machine at work a few months ago When compiling code on a remote machine, a terminal on one window would cause YouTube videos to lag on the other! As far as I could ascertain, there was simply no hardware accelerated playback going on. Both Chrome and Firefox had seemingly abandoned X11 for a Vulkan based render backend…
Firefox on X11 works fine if you enable media.ffmpeg.vaapi.enabled in about:config
Re: XFCE 4.20 aims to bring preliminary Wayland support
#13In all honesty, the screen sharing situation (and other stuff) in Wayland is currently so brittle that I consider XFCE (my daily driver) lagging behind in its adoption a feature.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#14If I had to use a Desktop environment in Linux, it would be XFCE. But, this Wayland thing is pushing me over to the BSDs. So far I have no abandoned Linux and I doubt Wayland will become mandatory until Firefox stops supporting X.
Don't look now: https://docs.freebsd.org/en/books/handbook/wayland/
Re: XFCE 4.20 aims to bring preliminary Wayland support
#15If I had to use a Desktop environment in Linux, it would be XFCE. But, this Wayland thing is pushing me over to the BSDs. So far I have no abandoned Linux and I doubt Wayland will become mandatory until Firefox stops supporting X.
I'm on X11 still and completely ignored the train wreck, hoping it'll go away eventually.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#16In all honesty, the screen sharing situation (and other stuff) in Wayland is currently so brittle that I consider XFCE (my daily driver) lagging behind in its adoption a feature.
I'm curious where you're having trouble. It seemed to me that this was quite bad at first (completely broken) and every application had to add explicit support, but I've had no problem with Firefox, Zoom and Slack recently. Just Microsoft Teams, but webcams don't even work in Teams.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#17To be clear here, we don't have a compositor yet. I've done a little work on it, but it won't be usable for at least a year, maybe (probably) longer.
4.20 will let you run some of our components on another compositor. We mostly test with Wayfire and Labwc, as our compositor will also be using wlroots.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#18[dead]
Re: XFCE 4.20 aims to bring preliminary Wayland support
#19In all honesty, the screen sharing situation (and other stuff) in Wayland is currently so brittle that I consider XFCE (my daily driver) lagging behind in its adoption a feature.
I'm curious where you're having trouble. It seemed to me that this was quite bad at first (completely broken) and every application had to add explicit support, but I've had no problem with Firefox, Zoom and Slack recently. Just Microsoft Teams, but webcams don't even work in Teams.
Not the GP, but I have a workflow that depends on the functionality in x11vnc, which allows me to script sharing of individual windows, regions, or desktops. AFAIK, nothing comparable exists in Wayland, and there isn't even the possibility to bring something like that to non-wlroots environments. So I'm stuck on X11 for now.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#20Genuinely find XFCE the only pragmatic option when it comes to "no-fiddling-just-working-and-lightweight" WMs in Linux/BSD land - it's basically like a better Windows 2000 UI with sane defaults throughout. Thanks so much to the devs involved in keeping XFCE up to date. This is major good news.