Live data from Hacker News

Sway 1.0

drewdevault.com

201–210 of 256 posts

Re: Sway 1.0

#201
post #62
post #39

Earlier quoted context omitted.

Based on Wayland, meaning it's more modern. Here's what I've heard for benefits: * Better multi-window and gesture support * Gaps built in (currently, i3 is separate from i3-gaps, which is what most actually use). No separate forks to deal with, meaning easier maintenance. * Wallpaper * Faster However, there are some big downsides. Wayland is still pretty beta, and not everything works well with it. This is not the f…

I've always wondered what's the use of gaps.

The desktop number 5 with cmus, alsamixer and a terminal music visualizer with gaps and transparency for eye candy.

Not everything needs to have a real use case!

Re: Sway 1.0

#204
post #128

Earlier quoted context omitted.

Personally for the most part I only have one application per workspace, and switch workspaces frequently. I often have several terminals on one workspace, though. I don't regularly use any GUI applications other than qutebrowser (web browser) and alacritty (terminal emulator).

how do you do password management? I setup Sway/qutebrowser last week and love it, but the lack of password management extensions was crippling. I reverted to Firefox + Vimium, which has been a subpar experience to qutebrowser. from what I understand the team on qutebrowser is actively working on an API for addons, but in the meantime it's a nonstarter for me. thank you for your contributions, by the way.

I keep a keepassxc open in the scratchpad, available with one keystroke on any desktop when I need it.

Workflow:

- site needs a login

- mod+- to get keepassxc to the front

- ctrl+f for search, typing the first letters of the service

- ctrl+c to copy the password

Re: Sway 1.0

#205

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.

I'm also waiting to get the scaling to work, but meanwhile this is my workaround:

- Firefox: about:config set layout.css.devPixelsPerPx to 1.5

- Emacs: Font size 16

- Terminal: Font size 16

- Signal: start with --force-device-scale-factor=1.5

Not perfect, but good enough for now.

Re: Sway 1.0

#206

Really exciting to see this released! Is there a good distro to run this on? I run Ubuntu at home but from my understanding, adding Sway to Ubuntu seems non-trivial. Is there a good distro I can switch to that supports Sway?

I'd wait for Ubuntu 19.04 to get wayland-protocols 0.17, which is required by wlroots. If you want to test it now, Arch linux has a package already:

https://www.archlinux.org/packages/community/x86_64/sway/

Re: Sway 1.0

#207
post #39

Earlier quoted context omitted.

Why should you (upgrade from i3/X)? What's the benefit?

Based on Wayland, meaning it's more modern. Here's what I've heard for benefits: * Better multi-window and gesture support * Gaps built in (currently, i3 is separate from i3-gaps, which is what most actually use). No separate forks to deal with, meaning easier maintenance. * Wallpaper * Faster However, there are some big downsides. Wayland is still pretty beta, and not everything works well with it. This is not the f…

HiDPI scaling is actually much better on Wayland than on X11. On X, if the app doesn't support HiDPI, the compositor cannot scale the window because it cannot scale input. On wayland, this is possible. Wayland also supports mixed-DPI multimonitor support. On weston, window dragging between mixed DPI monitors is seamless.

Re: Sway 1.0

#209
post #127

Earlier quoted context omitted.

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…

What I've been thinking is, why can't we have both? Imagine just two changes: a workspace's mode can be switched between tiling and floating, and additional workspaces are just windows. Now you can have any combination of floating and tiling that makes sense to you. You could, for instance, set your desktop to tiling mode and open two new workspace windows, the switch one to floating and run your GUI desktop stuff on…

I think AwesomeWM allows that

Re: Sway 1.0

#210

Earlier quoted context omitted.

I get the opposite feeling. I feel like I'm in a trash dump when I use an overlapping window manager, and have to sort through the pile to find what I need. Tiling window managers perhaps make more sense for devs or other professionals who use several of the same applications every day and know what window and pane they will be on, and can switch quickly with keystrokes. That being said, once you internalize the mode…

What I usually want to do is just click and resize to something that "feels right" for each of my programs, and then flip between them as needed, then resize again later as I workflow progresses. Often I want some important text from one to be visible while I'm working in another (thus overlapping), so I jockey them around until it feels right, and go.

I think the key difference here is the use of multiple virtual desktops in the tiling case. In my setup I typically have one vdesk for browsing, one for docs, one split between code/terminal. I may have others open for chat and music, and I can switch between any with one key combination, or resize with another. I love that when I open a new window it will maximize the screen real estate of wherever I put it.

Granted, I've been using i3 for more than half a decade, but I do agree with sibling posters on how 'freeing' the experience is once you get used to it. There is no doubt a learning curve; but in my experience it's on the order of days.

Post reply on HN