[AnonHP]

How is it on older or budget hardware though? It’s been a long time since I tried KDE, and in between even worked with Xfce because Gnome was a bit more resource intensive. Is it still the case that in terms of hardware specs and demand of the hardware, KDE needs/uses more than Gnome? I guess Xfce will be in a different league capability wise and resource requirement wise.

[yjftsjthsd-h]

AIUI, they actually really made an effort to improve on that front, to the point that KDE is actually really good about resource use these days, which is eg. why it was picked as the default for the pinetab 2.

[hedora]

I use LXDE on my new boxes, but on a 15 year old machine I wasn't sure what the Linux distro had defaulted to. I was surprised to see it was KDE. That machine takes 30 sec to decrypt the disk encryption key (stupid proof of work functions!), but the desktop environment is as snappy as LXDE on high-end 2026 machines.

I haven't compared those two with XFCE recently, but they all seem fine these days.

[71bw]

> That machine takes 30 sec to decrypt the disk encryption key (stupid proof of work functions!),

I think my Ryzen 7500F takes a similar amount of time and it is, by no means, old nor underpowered.

[hnlmorg]

I’m running it on a ~15 year old Intel NUC.

It’s got 4GB RAM and a modest Intel i3.

KDE runs flawlessly. While modern web browsers struggle with more than a few tabs open.

[bpye]

I run it on my RK3588 based MNT Pocket Reform. I have to force the GL ES 2 backend because of, presumably, Panfrost bugs, but otherwise it runs well despite the fairly weak CPU and GPU.

[pabs3]

Running it on a dumpsterd PC with a 2013 Intel CPU. Works fine.

[ryukoposting]

How old and what budget? I spent a good chunk of the late 2010s rocking Plasma 5 on a machine with a first-gen i5. It 8 GB of RAM and an SSD, which probably helped, but it ran great!

[dvdgsng]

If that counts for you, but I've just used it with CachyOS on a 2017 XPS with no issues and performance was great.

[monegator]

define older? no problem on my 2012 macbook