Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sway 1.0

drewdevault.com

Post reply on HN
Print view View original

171–180 of 256 posts

Re: Sway 1.0

#171

Post by ddevault »

mediocrejoker wrote: post #170
ilovecaching wrote: post #13

This is huge news. Sway is absolutely incredible, it puts macOS, built by Apple's army of engineers and dump trucks of money to shame in its simplicity, stability, and efficiency. If you want the best of the best DE, look no further. If you're on the fence about trying a tiling windows manager, I say, give it a shot for a single week and you'll never look back. Invest a few hours in a sway config file that will serve…

I tried to switch from i3 a few months ago and spent several hours trying to get it to work with my Nvidia card before finding out that the project doesn't support Nvidia for ideological reasons. I'm not well versed in the details of the conflict, and of course any open source project is not compelled to support anything they don't want to. That being said it would have been nice to know that they have no plans to su…

It merits re-empathising that it's Nvidia that does not support sway - not the other way around.

Re: Sway 1.0

#172

Post by vially »

Memosyne wrote: post #29

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.

This is the biggest issue for me as well, but I've mostly learnt to live with it by not scaling the HiDPI display in sway. What I do instead is scale the XWayland applications when possible.

For me the only XWayland apps that I want to use on the HiDPI display are Chromium and VSCode and both of them have options for scaling (e.g.: "--force-device-scale-factor=2" for Chromium; "window.zoomLevel" for VSCode).

Re: Sway 1.0

#173

Post by Spearchucker »

Worked hard at Microsoft and at Nokia. Held senior positions at both and maybe loved what I was doing too much to burn out.

That said I then took on some enterprise roles and the lax work ethic blew my mind. It was like a vacation. Eternal summer. I recommend it.

Re: Sway 1.0

#174

Post by peteforde »

Sir_Cmpwn wrote: post #126
peteforde wrote: post #117

Congrats on the release! You should be very proud of what your movement has accomplished. I want to highlight something that I appreciate in your release post, which is the short explanation between paragraphs 1 & 2: "Sway is an i3-compatible Wayland desktop for Linux and FreeBSD" One of my major peeves with OSS projects is the tendency to adopt an "if you're reading this, you already know what this is for" stance. I…

https://swaywm.org should cover this right?

Yes, that is the ideal place for all of the above questions to be answered. What you have there is a good start, with lots of room for expansion.

For what it's worth, I was browsing HN on my iPhone and wrote my comment on my desktop - which means that I did not perceive that you had a video. While this is easily addressed by providing an mp4 encoding alongside your webm, the types of information I'm suggesting you provide would weigh down a product teaser video heavily. The ideal product video is about a minute and focuses entirely on how awesome your life will be when you have access to Sway 1.0. All of the noob questions can safely be answered using text with hyperlinks.

Re: Sway 1.0

#175

Post by 7e »

ddevault wrote: post #171
mediocrejoker wrote: post #170

Earlier quoted context omitted.

I tried to switch from i3 a few months ago and spent several hours trying to get it to work with my Nvidia card before finding out that the project doesn't support Nvidia for ideological reasons. I'm not well versed in the details of the conflict, and of course any open source project is not compelled to support anything they don't want to. That being said it would have been nice to know that they have no plans to su…

It merits re-empathising that it's Nvidia that does not support sway - not the other way around.

The makers of the world's best and most popular graphics cards will never compromise their goals to accommodate an i3 clone. I think it's fair that the smaller entity support the larger one.

Re: Sway 1.0

#176

Post by kingaillas »

kstenerud wrote: post #36
NullPrefix wrote: post #27

Earlier quoted context omitted.

You know that there's multiple virtual desktops, right?

... which doesn't solve the underlying problem. I don't want to switch to a different desktop, such that my text editor window disappears and my terminal appears. I want them both on the same screen, along with my browser which points to a SO answer, in big sizes. In a normal window manager, this is accomplished by making them all big and then either overlapping them in ways that makes it easy to click on them, or ju…

I love tiling window managers. I spent way too much time in non-tiling managers optimizing window sizes and so on - basically my 80% usage is to split the screen in half, one app on the left, one on the right.

This is basically what I do at work on a Windows system, using the drag-to-left and drag-to-right.

For your example case, I'd split the screen with my editor taking up the left half, the split the right half into upper and lower, with SO answer in top half and terminal in bottom half. That's the quick and easy split, I could also fiddle with resizing (using arrow keys) the split a bit left/right or up/down.

This gets the info all visible at the same time, without clicking or tabbing to bring one window at a time to the top.

The usage I described above is what I do on my work machine using i3. I'm gonna try out sway now that it's 1.0!

Re: Sway 1.0

#177

Post by chmln »

rudilee wrote: post #55
ilovecaching wrote: post #25

Earlier quoted context omitted.

Because you can support Wayland and make Sway better. X11 is a super crusty, hacky mess that is being phased out. Sway also incorporates some nice features (gaps) that were previously not in the base version.

I really don't get it why people like gaps so much, yes it's look pretty, but in my opinion it is as much waste of space as window drop shadow. I would like to have as much screen real estate as possible to be used to show information, that's the whole point to use tiling wm in the first place for me.

A 5px gap between windows is a drop in the bucket, but adds a lot in terms of aesthetics.

Re: Sway 1.0

#178

Post by 7e »

jadbox wrote: post #35

Is there an update to the nvidia (proprietary drivers) situation with sway/wayland?

There may eventually be a solution where Wayland can run on top of Vulkan.

Re: Sway 1.0

#179

Post by ddevault »

7e wrote: post #175
ddevault wrote: post #171

Earlier quoted context omitted.

It merits re-empathising that it's Nvidia that does not support sway - not the other way around.

The makers of the world's best and most popular graphics cards will never compromise their goals to accommodate an i3 clone. I think it's fair that the smaller entity support the larger one.

Our policy bubbles down to wlroots, which is the basis of a huge variety of Wayland compositors.

However, we only need to support Nvidia if our goals include "adoption by Nvidia users". But they don't, so we aren't going to.

Re: Sway 1.0

#180

Post by newnewpdro »

7e wrote: post #175
ddevault wrote: post #171

Earlier quoted context omitted.

It merits re-empathising that it's Nvidia that does not support sway - not the other way around.

The makers of the world's best and most popular graphics cards will never compromise their goals to accommodate an i3 clone. I think it's fair that the smaller entity support the larger one.

This isn't an i3 vs. nvidia situation, this is linux kms/drm progress vs. nvidia.

nvidia is simply being uncooperative.

Post reply on HN