I find this project very interesting. Given that a slim KDE setup uses about as much ram as XFCE, aaaand XFCE is pretty much the "resource friendly" FLOSS desktop, I think it is safe to say:
* Linux does not really have a resource friendly desktop
* GTK based envs are not resource friendly (how else can XFCE be on par with KDE?)
* Qt has the best features/resources ration -- yet there is no resource friendly desktop based on it, until...
...LXQt! (okay maybe Trinity, KDE3's continuation, also counts)
Now on top of that Wayland is already slightly less resource consuming than X11, and has potential to be a lot less resource consuming in the long run, a project like LXQt-on-Wayland (LWQt) makes a lot of sense.
Many people in this thread asked what compositor was used. IIRC it was Mutter, as mentioned here:
Here's a discussion:
* Linux does not really have a resource friendly desktop
* GTK based envs are not resource friendly (how else can XFCE be on par with KDE?)
* Qt has the best features/resources ration -- yet there is no resource friendly desktop based on it, until...
...LXQt! (okay maybe Trinity, KDE3's continuation, also counts)
Now on top of that Wayland is already slightly less resource consuming than X11, and has potential to be a lot less resource consuming in the long run, a project like LXQt-on-Wayland (LWQt) makes a lot of sense.
Many people in this thread asked what compositor was used. IIRC it was Mutter, as mentioned here:
Here's a discussion:
Comment