A lot of Wayland compositors have a GLES 2.0 renderer which should be supported by ancient GPUs. If you try Vulkan based compositors you might be out of luck.
In my experience, projects going to Wayland actually improves performance and system resource usage. I got around 200Mb RAM back, when I switched from Qtile X11 to Qtile Wayland. 900Mb on XOrg, 700Mb on Wayland. These are with the same configuration and the same programs being autostarted.
Wayland does improve performance but only in some perspectives (for example, UI smoothness). In my case the negative impact looked like CPU overhead. It was easier to make the system stutter and some apps like Firefox worked more sluggishly. I suspect it’s because of how Wayland works fundamentally.
EDIT: you know the society is doomed when it downvotes comments about personal experience.
I highly doubt you can conjure up a Wayland compositor that consumes more than 1% of your CPU, even eye-candy nightmares like Hyprland will not have any significant CPU usage.
I ❤️ xfce, dying for Wayland. Wish I knew how to ninja together xfce Wayland. As most apps are now compatible.
please no, XFCE is my last refuge for machines too old to support Wayland
you understand that you can still use x11 with KDE or gnome right?
They’re not killing X11 support, don’t worry. They’re just expanding to Wayland support.
I am running Wayland on my 2013 MacBook Air. Joe old is your hardware?
GTS 450 lol
A lot of Wayland compositors have a GLES 2.0 renderer which should be supported by ancient GPUs. If you try Vulkan based compositors you might be out of luck.
Xfce is mostly used on older hardware. Dying to see how many times slower it’ll become on Wayland. I’m guessing 3x.
Why should it be slower?
Because I tried Wayland vs X11 on older hardware and sometimes it was noticeably slower?
In my experience, projects going to Wayland actually improves performance and system resource usage. I got around 200Mb RAM back, when I switched from Qtile X11 to Qtile Wayland. 900Mb on XOrg, 700Mb on Wayland. These are with the same configuration and the same programs being autostarted.
Wayland does improve performance but only in some perspectives (for example, UI smoothness). In my case the negative impact looked like CPU overhead. It was easier to make the system stutter and some apps like Firefox worked more sluggishly. I suspect it’s because of how Wayland works fundamentally.
EDIT: you know the society is doomed when it downvotes comments about personal experience.
I highly doubt you can conjure up a Wayland compositor that consumes more than 1% of your CPU, even eye-candy nightmares like Hyprland will not have any significant CPU usage.
I know and htop didn’t show 100% usage either. It just felt like CPU overhead.
blasphemy! Off with ur head! 🤣
Off with your head for supporting the accessibility nightmare that is Wayland :)
What do you mean by that? I’ve been using it in Plasma and haven’t had issues with it. Then again my use case might be different.
Do you use screenreaders?
I don’t.
I believe that tells enough.
Other way around