HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
swaywm
sway
C2015–2026
swaywm / sway

sway

i3-compatible Wayland compositor

93Distinct people
106Mentions
1Explicit recommenders
17.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

i3-compatible Wayland compositor

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I really love the syntax and performance of fish shell, I had a few bash scripts that were used to manage the system volume notifications and power/battery information, as I…

L0stLink used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year106 dated mentions

Observed mentions: 2015-08-16 19:36:44 UTC to 2026-03-20 13:37:33 UTC.

051015202015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 16 mentions; 1 submissions, 15 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 21 mentions; 2 submissions, 19 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 7 mentions; 5 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC110
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1019
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC10010
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC16115
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC21219
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC13112
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1019
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC10010
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC752
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC312
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
sway English - عربي - Azərbaycanca - Česky - Deutsch - Dansk - Español - Français - ქართული - Ελληνικά - हिन्दी - Magyar - فارسی - Italiano - 日本語 - 한국어 - Nederlands - Norsk - Polski - Português - Română - Русский - Српски - Svenska - Türkçe - Українська - 中文-简体 - 中文-繁體 sway is an i3-compatible Wayland compositor. Read the FAQ. Join the IRC channel (#sway on irc.libera.chat). Release Signatures Releases are signed with E88F5E48 and published on GitHub. Installation From Packages Sway is available in many distributions. Try installing the "sway" package for yours. Compiling from Source Check out this wiki page if you want to build the HEAD of sway and wlroots for testing or development. Install dependencies: meson * wlroots wayland wayland-protocols * pcre2 json-c pango cairo gdk-pixbuf2 (optional: additional image formats for system tray) swaybg (optional: wallpaper) scdoc (optional: man pages) * git (optional: version info) * * Compile-time dep Run these commands: meson setup build/ ninja -C build/ sudo ninja -C build/ install Configuration If you already use i3, then copy your i3 config to ~/.config/sway/config and it'll work out of the box. Otherwise, copy the sample configuration file to ~/.config/sway/config. It is usually located at /etc/sway/config. Run man 5 sway for information on the configuration. Running Run sway from a TTY or from a display manager.
Read the full README on GitHub

What Hacker News says

21 sources
> Power user functionality like copy paste on the other hand? https://github.com/swaywm/sway/issues/4007 might want to pray before using that. Come on. Congratulations, you've found the only opened bug report about clipboard on Sway/wlroots. It's triggered by edge cases (X11 client hanging + fcitx apparently), and most of it has been fixed already. Are you really trying to convince people that the clipboard is broken on Wayland with this? Maybe you could start by actually trying Wayland.
In On Abandoning the X Server
I can't find the story you're talking about here, but one thing that would be good to understand here is whether this is some flaw in the Wayland protocol, or whether this is an implementation issue in a specific Wayland compositor like Gnome's Mutter. People tend to blame a lot of issues resulting from immature implementations on some unspecified "Wayland" (whatever that means). All I can find is that in the past Mutter had lower latency for its Wayland implementation when compared to it using X.org, but it seems that Mutter's latency story has always been iffy in the past. FWIW it seems that Sway for example has finely grained input latency tweaks built in while being Wayland compliant [1]. [1]: https://github.com/swaywm/sway/releases/tag/1.4
In On Abandoning the X Server
> 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
In The X.Org Server Is Abandonware?
Yes. GNOME has its bundled screenshot tool, and Zoom supports screen recording on GNOME/Wayland. Sway has grim + slurp for screenshots, and wf-recorder or wlrobs for screen recording. However, one difference between X11 and Wayland, is that the role of the compositor (window manager) is much larger in Wayland. Thus, I believe it is up to the compositor to offer an API for features like this in Wayland, and the API may differ between compositors. In practice, GNOME has done their own thing; KDE and Sway collaborate on protocols, and are partly compatible; nearly every other compositor is based on Sway's wlroots, and should be compatible with Sway. [1]: https://github.com/swaywm/sway/wiki
In Some Ugly Code Can Get Nvidia's Linux Driver Working with Accelerated XWayland
I am not the author of dwl. Since dwl is based on wlroots (just like the popular Sway) it already supports making screenshots using grim[1] and screencasts using wf-recorder[2]. You can try out dwl from within your current WM. The default modkey is Alt. If you want to use the Super key, change `#define MODKEY WLR_MODIFIER_ALT` in `config.h` to `#define MODKEY WLR_MODIFIER_LOGO` and recompile. The default terminal emulator is kitty but you can change `termcmd` to alacritty if you want. Currently, only native Wayland applications run on it. You can enable experimental Wayland support for Firefox with `MOZ_ENABLE_WAYLAND=1`, see Running programs natively under Wayland in Sway Wiki[3]. Do not hover over the edges of windows – this will crash dwl. [1]: https://github.com/emersion/grim [2]: https://github.com/ammen99/wf-recorder [3]: https://gi
Read the rest
In Dwl: Dwm-like Wayland compositor based on wlroots
> If you have a problem that manifests itself under one DE but not under another, you are doing something very wrong - unless you are doing something very deeply integrated with specific DE. I see. So you're saying it's the "app developers" fault when a Linux user changes any system component of the Linux desktop stack i.e. display manager or desktop environment and the app fails to start or crashes because it only runs on GNOME, KDE or its X11 or Wayland-specific. It is actually an entire distro problem. When someone decides to make the switch to full blown Wayland or some other configuration, all bets and guarantees are off on stability and they start finding alternatives for other apps because the apps they tried don't work on their setup. [0] There's a reason why they say "UNSUPPORTED". For example, Firefox couldn't start on SwayWM an
Read the rest
d the number of issues and combinations of people not running it on their distro setup was mounting. [1]. Such issues are easy to test on Windows and macOS but very difficult in Linux distros, resorting to trail through the whole desktop stack to find the issue as demonstrated in this ticket [2]. Such issues like this still exist in many Linux apps not just Firefox. > Seriously, for a normal, user-facing app, all you should care about is at the level of the framework you used. Like I said, no guarantees are made if the user ends up changing system components or old frameworks and the app crashes on their setup when it is specifically made to work on a default install of XYZ distro. The point is that the freedom to mix and match subsystem components makes it complicated to test your app or trace a bug which could at worst be a regression in one part of a Linux subsystem component, which is why some see it as a blessing and a curse here. [0] https://www.swalladge.net/archives/2019/10/14/are-we-wayland... [1] https://github.com/swaywm/sway/issues/3115 [2] https://bugs.kde.org/show_bug.cgi?id=397834#c1
In WinUI – The modern native UI platform of Windows
> No, but having discussions somewhere completely unlinked to your open source repository https://github.com/swaywm/sway#sway > Join the IRC channel (#sway on irc.freenode.net). This is a clickable link. >without a searchable archive and no way to link to discussions does This misrepresents how IRC is supposed to work. You're not supposed to catch up on what you missed. You're supposed to have the conversation there. It's like chatting at the watercooler, not writing into stone. If you're "searching" the logs as part of your normal IRC routine, you're using IRC incorrectly. >> so you're not entitled to support, features, or yes, even explanations of why decisions were made >I was initially going to respond by saying "then you shouldn't ask for contributions". You're not entitled to it, but you might receive it anyway. And the only one of
Read the rest
these which relates directly to contributions is explanations - withholding features and support, in fact, leads to more contributions. I have written about this on my blog on several occasions if you want to learn more about this approach.
In The Sourcehut Project Hub
Being more specific would give away my identity, but this is one issue I ran into while moving from i3 to sway: https://github.com/swaywm/sway/issues/1005#issuecomment-3315... where the comment that closes the issue just says "we'll never implement this, issue closed". I sympathize with you in that, if you had little time and other things to attend to, then just closing an issue is an instant reward of having something less to do. But I think it would have been better to, first, don't do anything about that issue if you didn't had the time to do it properly (even if you were the one that filled the issue!), which would have been to write down the rationale why you think that feature is not worth its tradeoffs, and also, to have let other users speak up their mind, and see what others think, before making a decision. For me, that differenc
Read the rest
e in "project culture" is the difference between an open source project that's worth contributing to, and one that is not. I've grown a couple of very large open source projects, and some of them I look at once a year, and they keep growing with dozens of PRs per week or day! The main reason I am able to just move on to other things is because I've grown and mentor the new maintainers and leaders of these projects , and I know they both carefully listen to the projects users, and are able to grow new contributors, just like I did.
In The Sourcehut Project Hub

Showing the 15 most recent of 21 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.