Some windows are more efficient to use when they are a certain size or shape, such as where text is made to wrap at a comfortable width for reading. Efficiency of screen pixel usage isn't the only factor affecting efficiency of the interface in practice.

You can resize, tab, and float windows in sway. You can also scale individual applications. There's nothing you can do with dragging that you can't do in sway faster with less presses and with saner defaults.

You can scale applications independently when they are floating. But that will affect the layout of other tiled windows on the same screen, as they will tile behind the floating window. So you would need to float everything. In that case it is not being a tiling WM

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.

Another thing to consider:

Even if there were a significant difference one way or the other, it's rare to spend more than 1% of your time arranging your workspace and switching views & windows, so any optimization of that 1% will have minimal effect on your productivity.

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