4 ms·

Meh, I want a window manager, not a full desktop environment. I want key-combo switching between apps and allowing the apps to be moved and sized. And that's it

by uticus 3y ago

Meh, I want a window manager, not a full desktop environment. I want key-combo switching between apps and allowing the apps to be moved and sized. And that's it. No need for special 'start/run' features, for DE-bundled apps, for DE-based widget bars, for DE-based notifications, etc. Get everything out of the way for focusing on the apps and allowing interaction between them only as needed. The problem imo is that Wayland is too hard to write your own WM for. People wrote X11 WMs in weekends when they got fed up with the status quo. How many do the same for Wayland?

creatonez 3y ago
KDE is modular, a significant amount of that can be removed cleanly. It's not quite as modular as LXDE or Xfce mainly because the binaries for Plasma and KWin-Wayland are handling a bit more than expected, but does it really matter on modern hardware that Plasma has a tiny bit of panel-related code loaded into RAM when your panels are disabled? (I'd probably say this is the worst non-modularity, and it's still avoidable if you're willing to swap out plasma for something else) > How many do the same for Wayland? A lot, because wlroots provides a decent base to handle all the things you don't want to be handling manually. The ecosystem of simple tiling WMs made with wlroots is quite vibrant.
- uticus 3y ago
  I stand corrected re my comment about making a compositor. At first, I was going to point out that wlroots itself says it abstracts the job of a compositor: 'about 60,000 lines of code you were going to write anyway.' [0] Would seem to prove the point that too many LOC are needed just to get something running. But really wlroots is from the same group that maintains Wayland [1], so maybe it's like a low-level/high-level access duality common in other software projects. [0] https://gitlab.freedesktop.org/wlroots/wlroots https://gitlab.freedesktop.org/wlroots/wlroots [1] https://www.freedesktop.org/wiki/Software/ https://www.freedesktop.org/wiki/Software/

by uticus 3y ago

creatonez 3y ago

KDE is modular, a significant amount of that can be removed cleanly. It's not quite as modular as LXDE or Xfce mainly because the binaries for Plasma and KWin-Wayland are handling a bit more than expected, but does it really matter on modern hardware that Plasma has a tiny bit of panel-related code loaded into RAM when your panels are disabled? (I'd probably say this is the worst non-modularity, and it's still avoidable if you're willing to swap out plasma for something else) > How many do the same for Wayland? A lot, because wlroots provides a decent base to handle all the things you don't want to be handling manually. The ecosystem of simple tiling WMs made with wlroots is quite vibrant.

uticus 3y ago
I stand corrected re my comment about making a compositor. At first, I was going to point out that wlroots itself says it abstracts the job of a compositor: 'about 60,000 lines of code you were going to write anyway.' [0] Would seem to prove the point that too many LOC are needed just to get something running. But really wlroots is from the same group that maintains Wayland [1], so maybe it's like a low-level/high-level access duality common in other software projects. [0] https://gitlab.freedesktop.org/wlroots/wlroots https://gitlab.freedesktop.org/wlroots/wlroots [1] https://www.freedesktop.org/wiki/Software/ https://www.freedesktop.org/wiki/Software/