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
21–30 of 204 posts
Re: XFCE 4.20 aims to bring preliminary Wayland support
#22If 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.
Could be worse. The whole Gnome 3 and Wayland thing pushed me to macOS.
I'm quite disillusioned with desktop computing in general. Microsoft and Google are leading the way with "enshittification" (https://en.wikipedia.org/wiki/Enshittification), and the Mac experience in 2024 isn't like what it was in 2009 when the Mac was at its peak, in my opinion. The Linux desktop ecosystem suffers from a lack of funding relative to its commercial peers, combined with the "organization from chaos" that comes with bazaar-style development. The X11 to Wayland transition would be easier to pull off if the Linux desktop has Microsoft- or Apple-levels of funding and cooperation, but such funding doesn't exist, and part of the characteristic of the bazaar is that developers and teams of developers get to work on projects of their own interest and its the community that "votes" on projects by using them. The bazaar definitely exhibits freedom, but the major downside is that major changes in infrastructure (such as the X11 to Wayland transition) could take a lot of time and have major pain points (for example, the development of incompatible Wayland compositors and the fact that the X11 concept of a window manager doesn't exactly translate to Wayland's concepts).
I love free, open source software, but I'm drawn more to cathedral-style projects such as the BSDs and HaikuOS where there is a coherent vision for the system. Unfortunately the BSDs are dependent on the broader FOSS ecosystem for desktops, which is dominated by the GNOME/KDE/Wayland ecosystem (which also priorities Linux and treats other Unix-like operating systems as an afterthought, but that's another discussion). I'll need to re-investigate HaikuOS to see whether it can be used as a daily driver today; I've seen that a lot of attention has been given to HaikuOS in recent years.
I'm slowly working on a side project where I'm implementing my dream OS, which is influenced by various alternate paths of workstation and desktop computing explored in the 1980s and 1990s but were overtaken by Windows and Unix, namely Lisp machines, the Smalltalk environment, and 1990s Apple initiatives such as OpenDoc and the original plans for the Newton, which involved a Lisp OS (https://mikelevins.github.io/posts/2021-07-12-reimagining-ba...). But I have a busy day job and so this will take years of effort on the side.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#23XFCE 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
#24Earlier quoted context omitted.
Yeah, it's pretty much the same story for me; after having found out how to get all the same features in KDE that I had in xfce, there was no way back. I always like to use the lightweight and less resource intensive software, but arguably not using hardware acceleration is actually very resource hungry.
> I always like to use the lightweight and less resource intensive software, but arguably not using hardware acceleration is actually very resource hungry. What hardware are you using where KDE is considered "resource intensive", yet it also has a GPU that supports Vulkan and hardware video decoding? I've used KDE for a long time, and can't remember a time when I noticed its resource usage (and I used to daily drive…
Normally it's a bit tricky to calculate memory blame between X11, the WM, and the shell, since often their allocations are actually on behalf of an application, and killing the application will reclaim it.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#25In 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
#26I've been using it for years and years. I started when it was the only lag free WM I could run on an atom powered netbook (the only "pc" I had at the time)!
Now many years later im still using it, and it still makes me happy. I'm not sure if people know what it's like to be able to click on something and have it work instantly with no lag.
It is a great piece of software, thank you to all the Devs who work on it!
Edit: I've seen a few complaints about hidpi. I'm not sure if this helps, but I have a 4k laptop screen, usb-c to a 4k monitor, and hdmi to a regular 1024 monitor orientated vertical.
By setting x2 in the appearance settings both the 4k monitors look beautiful, and then in the screen manager (where you can move around the screens and set orientation, I just have to set 2x scale on the 1024 monitor and it's fine. Like obviously less good than the 4ks... But it is a worse monitor. I'm surprised it all works so well to be honest!
Re: XFCE 4.20 aims to bring preliminary Wayland support
#27If 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 haven’t figured out the magic dbus (I guess) incantations required to make screen sharing work without systemd though. I guess it needs pipewire at least.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#28Why should old WMs/DEs add support for Wayland, why not just write new for Wayland specifically?
The only component that requires major changes is the WM. Otherwise, for the rest of them, it's more about fixing platform specific quirks.
(Ok, we did have to write an embedded compositor library for our panel to use, but... yeah.)
Re: XFCE 4.20 aims to bring preliminary Wayland support
#29Do I understand correctly that they are building on top of wlroots? If so, I am pretty happy about this development as I might get to enjoy the solidity of XFCE apps in other WMs / compositors like Sway or River.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#30Does anyone a cleaner article?