XFCE 4.20 aims to bring preliminary Wayland support
ostechnix.com
XFCE 4.20 aims to bring preliminary Wayland support
1–10 of 204 posts
Re: XFCE 4.20 aims to bring preliminary Wayland support
#2I still remember seeing a video of Xfce (I think it was version 4.0.4) and being amazed how simple and reliable you could pick your own launchers and widgets on the bar. For me it was much simpler than Gnome at the time.
Modern KDE looks sometimes like Xfce for me (just my feeling, don't bite me), but somehow I always get a lot of strange bugs when I try to change things. Xfce had its own problems (I remember when Thunar was quite unstable), but it still is my go to desktop for simplicity and reliability.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#3When 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 on Wayland
After leaving KDE 5 to "marinate" overnight (I use Gentoo, so compiling an entire desktop environment like KDE can be time consuming) everything "just worked"
I miss the visual simplicity of XFCE and I'm hopeful to return to it one day, but in the interim, responsiveness is key
Re: XFCE 4.20 aims to bring preliminary Wayland support
#4Re: XFCE 4.20 aims to bring preliminary Wayland support
#5But, 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.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#6XFCE 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…
Re: XFCE 4.20 aims to bring preliminary Wayland support
#7If 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.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#8If 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.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#9I mained dwm some years ago and I like it, but if I just need a quick environment I usually go back to Xfce. My family's computers (my dad's, my mom's, my sister's and my media PC, because I was lazy) are all Xfce. I will consider switching to Wayland when Xfce will support it. I still remember seeing a video of Xfce (I think it was version 4.0.4) and being amazed how simple and reliable you could pick your own launc…
same.
why?
they all grew up on Win9x and the visual metaphors used by XFCE just click, they could all care less what's behind the scenes as long as YouTube and Facebook work.
p.s. dwm is great. most suckless stuff is.
Re: XFCE 4.20 aims to bring preliminary Wayland support
#10XFCE 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…
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.
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 a ThinkPad X200 as late as 2016)