3 ms·

I boot straight into the console and then have a setup where I either run startx or start_sway. I love i3 and it was my first experience with tiling WM years a

I boot straight into the console and then have a setup where I either run startx or start_sway. I love i3 and it was my first experience with tiling WM years ago. It is absolutely a radical break for me from all other WM's since tiling allows me to work in deep focus many desktops, 1 desktop per activity/task and my focus always on one thing not many. Also wanting not to miss out on the future I moved to sway in parallel. I am literally in sway 90% of the time. The only difference is if I have to use video / webRTC screensharing or similar (usually in the browser), in which case sway will not work. This is why I maintain a dual system of both i3/sway. Also I trust i3 to be more stable for when I am standing in front of a crowd or have to connect my system to a variety of different external beamers, monitors etc. It sounds nuts to "maintain" 2 WM's but my configuration and workflow never deviates no matter which system I use even across upgrades of i3/sway. When I plug in a new freshly installed machine I just fetch my dotfiles and have both i3/sway in exactly the same way as I'm used to ... It's incredibly easy keeping both around if one has to (or wants to). Bonus of sway is also that it has gaps support (which is cool on bigger screens, less important on laptops). edit: both sway / i3 gave me no problems at all running them under restrictive environments such as LD_PRELOAD=libhardened_malloc.so (from GrapheneOS) and also work with under firejail without problems. I'll stop since it's anyway clear I am a big fan of both :)

Arnavion 6y ago
>The only difference is if I have to use video / webRTC screensharing or similar (usually in the browser), in which case sway will not work. Screensharing under sway works fine with firefox and chromium through xdpw.
- DyslexicAtheist 6y ago
  thanks for the pointer, haven't tried this yet. cool!
grep_name 6y ago
> 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.

Arnavion 6y ago

>The only difference is if I have to use video / webRTC screensharing or similar (usually in the browser), in which case sway will not work. Screensharing under sway works fine with firefox and chromium through xdpw.

DyslexicAtheist 6y ago
thanks for the pointer, haven't tried this yet. cool!

grep_name 6y ago

> 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.