I´m willing for LXQT, aren´t you?

[maka]

Gnome has win popularity for our boxes because of wayland replacing XCFE. The reason is that panfrost driver works much better with mali in wayland. But LXQT has reached wayland now and is a true lighter desktop. When 2.1 gets the repo this will become true.

Edited November 8 by maka

[robertoj]

How do you measure “lightness”? I use openbox, but I want to try Wayland now.

[maka]

You know is light when your pc is responsive and temperature is lower. I don't use any software but there is so much difference that you know.

 

[Hqnicolas]

ok... I think this LXQT will make the Joshua Riek project better for RK3566 and RK3576
armbian was alleady light interface with "fake ubuntu"
https://github.com/Joshua-Riek/ubuntu-rockchip/issues?q=LXQT
nobody's talking about. @maka can you talk with him?

Edited November 17 by Hqnicolas

[maka]

Another reason to change is that gnome interface does not work anymore on some rockchip cpus like rk3566 and 3576.

[eselarm]

I have used LXQT in the past (decade ago maybe) but I mostly use KDE nowadays. (currently KDE6 on N100-8GB and z8350-4GB). For my new ROCK3A I booted the KDE Neon Noble based desktop image on my ROCK3A (2GB RAM, older Sandisk 32GB SD-card). This is 2GHz RK3568 and was surprised how well that worked.

I did buy the ROCK3A for SPI-flash, U-boot, SATA, server, KVM operation, but it is great that also KDE6 works on it. I was mainline based kernel 6.6.62, I might try again with 6.1.84, but that will mainly be to see how well I can get the video codecs to work (in browser, but also as server-like for jellyfin). Same for RK3588-8GB, that is also OK for 'heavy' YouTube etc.

[maka]

What do you mean by heavy youtube?

[eselarm]

Quote

What do you mean by heavy youtube?

That is hard to say as every has likely their own google-specific account experience. And/or lots of ads loading in the background, that kills performance.

More specific to what Youtube originally is (or was?) is playing a video. Now that is even harder to say something about, as resolution, frame-per-second and codec are an important factor. It is 4k60fps VP9 on a Soc with no working VP9 HW decoding for example. Or 720p30 h264 done SW decoding. Etc.

So the DE might be light, if use-case is mostly webbrowser usage, that will determine the experience of slow or fast.

But I do not know what your use case is. I use some basic local homeautomation webserver for example, so easy for a simple low-cost SoC.