3 ms·
One thing I've noticed (and irritates me) about Wayland is how now your WM is actually effectively now your DE and your Xserver. So if you want to use Sway, yo
by suvelx 10y ago
One thing I've noticed (and irritates me) about Wayland is how now your WM is actually effectively now your DE and your Xserver.
So if you want to use Sway, you better get used to configuring your displays in a config file.
What about applications that need to set environment variables (e.g. gpg-agent, gnome-keyring) how do you launch them if your compositor doesn't launch and export them for you? (That said, I still can't work out where gnome-shell decides to launch gnome-keyring-daemon on login)
Ideally, I'd like a DE that provides display/audio/power/menu management, but with a (manual) tiling compositor that supports window stacking/tabbing (like i3/sway). And bonus points if it has a sloppy floating-desktop mode.
Shelltile kinda works, but shits the bed when applications set window size hints, and there's no window stacking/tabbing.
- bitwize 10y ago> One thing I've noticed (and irritates me) about Wayland is how now your WM is actually effectively now your DE and your Xserver. A deliberate design decision intended to keep context switches off the hot path. It's one of those "just trust me; this way really is better" things. You're sacrificing very little to get an improved graphics stack.
- rrix2 10y agoYou're sacrificing composability, one of the biggest things that makes GNU/Linux so powerful in my mind. Right now, I'm running AwesomeWM embedded in a KDE session. As a result, I have a lean tiling window manager which I can configure to my liking, and a bunch of shit that I don't care about to that same level "just works" and is integrated in to the session like display management, network connectivity, even notifications daemon are a problem on other minimalist desktops that would have to be fully reimplemented for each Wayland WM.