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

10 sources
GitHub wikis are already accessible over Git in a separate repo, as advertised via the “Clone this wiki locally” sidebar link: e.g. the wiki at https://github.com/swaywm/sway/wiki can be cloned from https://github.com/swaywm/sway.wiki. (Of course, people have also made a variety of Git-based Web authoring tools spanning from CMSes to wikis, but I can’t say I’ve seen one that really worked out—Git’s capabilities seem too powerful to be tamed in a reasonable Web-based editor. The most elegant way to link from a website to its Git version history that I’ve seen is on Yannik Sander’s blog[1].) [1] e.g. https://blog.ysndr.de/posts/internals/2021-01-01-flake-ifica...
In Git Notes
I'm curious about this as well, but wouldn't be pointing fingers at the Wayland developers. See, for example, one of the most recent comments in the discussion linked to in the parent post, by Nilvus, one of the (wise and knowledgeable) darktable developers: > The only thing is that color management for Wayland is progressing and far from being completely done. Even if work is quite slow, things seems to go in good direction. For correct and complete Wayland color management, we just have to wait again. Blender itself seems to be color-profile aware: https://docs.blender.org/manual/en/latest/render/color_manag.... Here is an issue tracking work on Wayland: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m.... There's a nice site which is parallel to this work which summarizes issues/goals: https://gitlab.freedesktop.org/pq/colo
Read the rest
r-and-hdr Here is parallel work on this in Sway: https://github.com/swaywm/sway/issues/1486 And parallel work in KDE: https://bugs.kde.org/show_bug.cgi?id=439135 I can't find any reference to color management in the Blender meta-issue at https://developer.blender.org/T76428. For X11, I believe applications would have to manually determine the color profile of the display holding the current window, then query colord or and X atom to determine the profile. The application would then manually do the colorspace conversion. Does querying colord and making an in-application conversion works for Wayland until Wayland becomes colorspace-aware? Or if there are more wrinkles?
In Blender: Wayland Support on Linux
Under GDM you can use systemd environment.d(5)[1] to configure those variables. I have some examples in my dotfiles[2]. Your Sway configuration also has to inject it's own environment variables to systemd session like is documented here[3]. Arch Linux does that in `/etc/sway/config.d/50-systemd-user.conf`[4] If you really want to run some shell scripts before sway then you have to create a new desktop file under `/usr/share/wayland-sessions/` that calls your script that setups environment and does `exec sway`[5] [1]: https://man.archlinux.org/man/environment.d.5 [2]: https://github.com/artizirk/dotfiles/tree/master/.config/env... [3]: https://wiki.gnome.org/Initiatives/Wayland/SessionStart [4]: https://github.com/archlinux/svntogit-community/blob/package... [5]: https://github.com/swaywm/sway/issues/100
In An X11 apologist tries Wayland
I really don't think this is correct. It is possible that you're just not able to notice the blurriness due to the scaling method used, the resolution of the display and the fact that text rendering tends to be blurred nowadays anyway [0], but I'm 95% sure that you'll be looking at blurred output, as documented [1]: > An integer is recommended, but fractional values are also supported. If a fractional value are specified, be warned that it is not possible to faithfully represent the contents of your windows - they will be rendered at the next highest integer scale factor and downscaled. I've just tried it again myself and can observe the downscaling. I can provide screenshots later demonstrating the scaling artifacts if anyone is really interested. [0] I configure my systems to perform crisper font rendering using `FREETYPE_PROPERTIES=tru
Read the rest
etype:interpreter-version=35`, along with some extra fontconfig options. This results in glyphs being aligned with actual pixel boundaries, reducing the need for antialias blurring. [1] https://github.com/swaywm/sway/blob/445bc2a943d905a0e5b1dc60...
In Are We Wayland Yet?

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.