3 ms·

> I boot straight into the console and then have a setup where I either run startx or start_sway Interesting, I do the same thing but just use startx. I find i

> I boot straight into the console and then have a setup where I either run startx or start_sway Interesting, I do the same thing but just use startx. I find it hard to find convincing reasons to move from X apart from it 'being dead,' which isn't very convincing to me. What benefits to you get from sway in your setup? Is it compatible with things like ssh X forwarding?

DyslexicAtheist 6y ago
:) literally no reason other than curiosity and a strong will to get that yak shaved. I don't hink X is dead for a while. There is a lot of reasons for application devs not to support sway unless a strong enough user-base from that camp justifies the effort. Consider also that some of the heavy lifting previously done by X is being offloaded to Sway. My motivation to switch to it was because Sway claims that you can just drop in your .config/i3/config and sway will be compatible to it. (it's pretty close). What I wanted was transparency (not via a clunky workaround like compton). Also a system that takes less of my resources while in use to also roll it out on 10 or 15 year old machines I own. Sway delivers here and also has less issues with screen tearing than X with my card. Literally everything I needed previously worked in Sway (often with different commands, e.g. wofi instead of rofi, or grim for screenshots, Waybar instead of Polybar, etc) anything else like tmux, ssh-forwarding and all things in the terminal work perfectly.