What does HackerNews think of sway?

i3-compatible Wayland compositor

Language: C

For what it's worth, Page Visibility doesn't detect switching windows under the Sway Wayland compositor. It does detect switching tabs within the same window.

https://github.com/swaywm/sway

I have been playing under sway which removes many bottlenecks (or at least haven’t noticed any), you could give it a try https://github.com/swaywm/sway
Oh, I'm sorry. I've totally wrong for a while then. Yes, written in C, 97.5% C.

https://github.com/swaywm/sway

Sadly it's bound to X11.

The alternative for me was to migrate to sway[1] to have a similar environment in wayland.

[1] - https://github.com/swaywm/sway/

> How's the forced v-sync?

Not sure what you're talking about. Haven't noticed any adverse negative effects.

It's super nice to have a desktop without any tearing though.

> I assume all games run XWayland, which makes it a non-issue.

I don't do PC-gaming.

> Also, can you use xdotool for key input redirection

Not sure what xdotool is.

I'm using sway[1] with libinput. I haven't had a need to use external tools beyond what they support natively.

> or screen capture programs and stuff yet?

I have no issues to do screenshots ad-hoc (in fact, I have keybindings to do this, and throw it right in the wayland clipboard).

I do notice that most Xwayland-based programs which tries to do screen-sharing fails spectacularly though.

[1] https://github.com/swaywm/sway

> Do you use a tiling window manager?

I have been more than happy with xmonad, my current tiling window manager [1]. I have been wanting to give sway [2] with Wayland a go as well. I like using it due to the lack of distracting animation and having great keyboard support, allowing me to be more productive — or at least feel like I am.

Besides servers, I didn't really do much with Linux until a year ago or so. I ended up picking Arch after seeing Jon Gjengset's stream [3] and it having great documentation. Still, it was a bit of a surprise to be met with a blank screen after installation.

1. https://i.imgur.com/TwiH6ks.png

2. https://github.com/swaywm/sway

3. https://youtu.be/ycMiMDHopNc

There's a lot of fun projects you can contribute to in the Linux Desktop space. I own the code in the GitHub orgs altdesktop <https://github.com/altdesktop> and dbusjs <https://github.com/dbusjs> and I'm very responsive on issues and pull requests. Another great community is sway <https://github.com/swaywm/sway/> and i3 <https://github.com/i3/i3>.
Spectacle is another alternative on macOS [1]. There's also Amethyst. I'm not sure which one's best. It is a matter of getting used to the default keybinds IMO.

With Spectacle, the default keybinds are using Alt and Cmd as super key. I like that one; I rather keep Caps Lock as Esc (else I'd use it as Ctrl).

As for i3, there's a backwards compatible Wayland successor called Sway [2].

[1] https://github.com/eczarny/spectacle

[2] https://github.com/swaywm/sway

Unsure if you've seen it before, but I've been using sway [0] as a Wayland-based replacement for i3. Switching the configs took about 15 minutes (and could probably be replaced by a few sed commands). It's been very nice to use all around--snappy, no major issues even with multiple monitors, etc.

[0]: https://github.com/swaywm/sway

> Anybody else have thoughts/plans on the future of X if Wayland really does take over?

I have been thinking about this for a few years at least (happy i3wm user).

I am looking at moving to Sway https://github.com/swaywm/sway (drop in replacement) at some point as it seems the development is really healthy. sircmpwn (Drew DeVault) has done a lot of really nice contribution to the FOSS community, in particular wlroots https://github.com/swaywm/wlroots I also thoroughly enjoy reading his blog https://drewdevault.com (articles from there often get posted here) there has been many a time I've read something he's written and thought "hear hear" in my mind.

It is also impacting my purchasing choices in regard to going for AMDGPU instead of NVIDIA for my next system that I plan to buy in a few months (mostly waiting for 3rd party Navi cards at this point).

That's not quite true: the compositor needs to support it. There's a protocol [1] for it that's supported by a redshift with a patch [2]. It also works out the box for any wlroots-based [3] compositors, like sway [4].

[1] https://github.com/swaywm/wlr-protocols/blob/master/unstable...

[2] https://github.com/minus7/redshift/tree/wayland

[3] https://github.com/swaywm/wlroots

[4] https://github.com/swaywm/sway