Live data from Hacker News

Sway 1.0

drewdevault.com

231–240 of 256 posts

Re: Sway 1.0

#231
post #127

Earlier quoted context omitted.

I really don't get the benefit of a tiling window manager. I tried one and instantly felt boxed in. There's not enough room on the screen for everything I need to have opened and flip between, which is why I use an overlapping window manager in the first place.

With a tiling window manager, every window you open has cognitive overload. Which workspace, which location on screen, is it okay if other windows resize, or do I have it float even? Every tile you add affects the other tiles in some way - at the very least a new tile (e.g. on a new workspace) consumes space that cannot be taken by other tiles. The reward for this additional cognitive load is that every action is con…

> With a tiling window manager, every window you open has cognitive overload.

I've been using a tiling window manager (XMonad) for ~3 years now; this is definitely true for the first few days (or weeks/months) until you adjust. After that, there is less overhead as you become more familiar with how the window manager behaves.

But this is also true for stacking window managers.

> With a stacking window manager, the cognitive overhead of opening a window is much less.

I think the level of cognitive overhead involved comes down (in the case of tiling window mangers) to what window rules you have, what kind of bindings you have set up to navigate between windows, etc., and how comfortable you are with those rules and bindings; the less comfortable you are, the greater your cognitive load will be when trying to use them.

Again, this is also true for stacking window managers.

> Every new window on the stack doesn't affect the others you were using.

Unless it "steals" focus and blocks the window you were working on. But that's expected behavior in a stacking window manager, so it's not much of a disruption. And it's one a user will certainly be aware of when opening a new window.

And this can (and usually is) be true for tiling window managers as well.

> I see a lot of people that respond to you by appealing to some objective superiority of tiling window managers, but there's advantages and disadvantages to both.

Right. There are pros and cons to each and really, but most people just don't really care that much about what window manager they're using.

I do want to add that one of the biggest pros to a tiling window manager (and a few stacking WMs) is the amount of customization available; if you're using a WM like XMonad, i3, Sway, bspwm, herbstluftwm, etc., you can configure the WM to do basically anything (including behave like a stacking WM), while many stacking WMs are fairly limited in how much customization they can have.

But that makes the assumption you're interested in customizing, which not everyone is.

Re: Sway 1.0

#232
post #66
post #41

Earlier quoted context omitted.

The author still flat-out refuses to support them. This might change if Nvidia open-sources their drivers, which I suspect is part of what he's trying to do.

Probably, but given the relative levels of adoption of Nvidia graphics cards and Sway, I suspect that he's doing more to limit adoption of Sway than he is of encouraging Nvidia to change their behavior.

I would say it's the case in both accounts.

Whereas before installing nvidia proprietary drivers was just a nuisance, now I am looking for alternative GPUs as I use Linux on all my machines.

Re: Sway 1.0

#233
Does anyone use Sway (or a tiling wm) mostly with graphical applications? Sway is tempting since it supports some niche features other Wayland compositors may never support, like cursor hiding à la unclutter and real redshift. I use a terminal everyday, but I don't mostly use a terminal.

Re: Sway 1.0

#235

Does anyone use Sway (or a tiling wm) mostly with graphical applications? Sway is tempting since it supports some niche features other Wayland compositors may never support, like cursor hiding à la unclutter and real redshift. I use a terminal everyday, but I don't mostly use a terminal.

I use vim so I use a terminal nearly all the time. But I also do non terminal things and none of my personal computers have anything other than i3. If I only needed tiling in a terminal I would just use tmux

Re: Sway 1.0

#237

What's the status of blurry XWayland applications on HiDPI screens? I tried to replace i3 with sway a couple months ago and couldn't get VSCode to look decent with scaling.

The trick is not to depend on pixel scaling (unless you have multiple screens at different pixel density), but to set the DPI for all toolkits ( GTK, Qt,...) to the correct value. See https://wiki.archlinux.org/index.php/HiDPI on how to do that. For most parts setting an environment variable is sufficient. Takes you a long way. Older apps can be often scaled by setting DPI in X and use XWayland.

Re: Sway 1.0

#238
From the faq:

"Tip: buy your hardware with open source support in mind."

Is it really necessary to put statements with such a condescending tone? Am I the only one who thinks that it can only hurt a project in the long term?

Re: Sway 1.0

#239
post #129

Earlier quoted context omitted.

Tabs are a completely different metaphor to tiles.

They are an example of managing content without overlapping windows. i3, Sway and Xmonad all have good support for them.

True, but Openbox, Fluxbox, etc. support that, without being tiling window managers. Heck, even Windows 10 now has support for window tabs :D

Re: Sway 1.0

#240
post #89

Earlier quoted context omitted.

I wasn't actually the original poster :) The thing is, we have studies that prove that mouse + keyboard interaction is faster than keyboard-only https://www.asktog.com/TOI/toi06KeyboardVMouse1.html - until you become super proficient with all the relevant the keyboard shortcuts. So it's not about "inferior"/"superior", it's about your use case.

> The thing is, we have studies that prove "Originally published in the AppleDirect, August, 1989 "

So? Do you think that users have changed so much in these past 30 years? If anything, things have regressed in some regards, as kids these days start directly with touch interface, single user, single application/windows OSes, basically, smartphone OSes (I know that technically mobile OSes are not like that anymore, but that's how they're used 99,999% of the time).
Post reply on HN