4 ms·
You're right and the memory use of KDE, GNOME, XFCE is unjustifiable. Even sway (the i3-inspired Wayland compositor) uses a lot of money for a simple tiling com
by cm3 10y ago
You're right and the memory use of KDE, GNOME, XFCE is unjustifiable. Even sway (the i3-inspired Wayland compositor) uses a lot of money for a simple tiling compositor that doesn't have fancy "bling". It's three times the memory use as xmonad and xmobar, but maybe it's an architectural issue with wayland. I mean, Weston isn't light-weight either.
- gnarbarian 10y agoGive lxde a shot then.
- cm3 10y agoI never felt comfortable with desktop envs, going back to KDE1 in the 90s. Used FVWM, Enlightenment, WindowMaker, LarsWM, Ion, WMI, DWM, spectrwm, Xmonad, sway, Weston, but never a desktop env due to missing flexibility and harder and harder config portability. My FVWM config still works, but GTK3 and GNOME configs are highly unlikely to work the same after 12 months.
- LukeShu 10y agoI don't use a DE, for much the same reasons you name, but I do use several pieces of LXDE, as they are generally built configurably and work well outside of the DE.
- gnarbarian 10y agoHey I hear you. I would say lxde is like e16 except less fancy looking. VERY basic. like, you get to write a script to bind the print screen key to take a screenshot.
- cesnja 10y agoWayland compositors must also do (some) actions that were previously handled by X server. Ergo your comparison is a bit unfair, you should try comparing sway vs i3 + Xorg.
- cm3 10y agoThat's what I suspected by saying "maybe it's an architectural issue with wayland".
- anewhnaccount 10y agoMore of an architectural goal than an architectural issue.