HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
swaywm
wlroots
C2017–2024
swaywm / wlroots · Archived

wlroots

A modular Wayland compositor library

35Distinct people
51Mentions
1Explicit recommenders
2.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A modular Wayland compositor library

GitHub

Where it is used

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

What people are saying

Games: yes, albiet mostly through Xwayland, which is a compatibility layer. Most games Just Work through this compatibility layer. OBS works fine, but you need a plugin.…

ddevault 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 year51 dated mentions

Observed mentions: 2017-10-19 17:28:42 UTC to 2024-10-15 06:43:18 UTC.

0510152017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024

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
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC13013
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC11011
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC11011
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC11011
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202

From the project README

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

Read the project’s introduction
wlroots ⚠️ Migrated to gitlab.freedesktop.org This project has migrated to gitlab.freedesktop.org. Pluggable, composable, unopinionated modules for building a Wayland compositor; or about 60,000 lines of code you were going to write anyway. wlroots provides backends that abstract the underlying display and input hardware, including KMS/DRM, libinput, Wayland, X11, and headless backends, plus any custom backends you choose to write, which can all be created or destroyed at runtime and used in concert with each other. wlroots provides unopinionated, mostly standalone implementations of many Wayland interfaces, both from wayland.xml and various protocol extensions. We also promote the standardization of portable extensions across many compositors. wlroots provides several powerful, standalone, and optional tools that implement components common to many compositors, such as the arrangement of outputs in physical space. wlroots provides an Xwayland abstraction that allows you to have excellent Xwayland support without worrying about writing your own X11 window manager on top of writing your compositor. wlroots provides a renderer abstraction that simple compositors can use to avoid writing GL code directly, but which steps out of the way when your needs demand custom rendering code. wlroots implements a huge variety of Wayland compositor features and implements them right, so you can focus on the features that make your compositor unique. By using wlroots, you get high performance, excellent hardware compatibility, broad support for many wayland interfaces, and comfortable development tools - or any subset of these features you like, because all of them work independently of one another and freely compose with anything you want to implement yourself. Check out our wiki to get started with wlroots. Join our IRC channel: #sway-devel on Libera Chat. wlroots is developed under the direction of the sway project. A variety of wrapper libraries are available for using it with your favorite programming language. Building Install dependencies: meson wayland wayland-protocols EGL and GLESv2 (optional, for the GLES2 renderer) Vulkan loader, headers and glslang (optional, for the Vulkan renderer) libdrm GBM libinput (optional, for the libinput backend) xkbcommon udev pixman libseat If you choose to enable X11 support: xwayland (build-time only, optional at runtime) libxcb libxcb-render-util libxcb-wm libxcb-errors (optional, for improved error reporting) Run these commands: meson build/ ninja -C build/ Install like so: sudo ninja -C build/ install Contributing See CONTRIBUTING.md.
Read the full README on GitHub

What Hacker News says

11 sources
I'm not sure why that's your takeaway here. Wayland exists precisely because things should easily mix and match - it should be easy to get your apps displaying/moving on any standard compositor. The same would go for other Freedesktop standards to do things like input, clipboard interaction, and screen recording. The only difference is that all these things currently used to exist within the X.org project, and now they're in various other places (some parts in fact don't exist at all...). There's nothing stopping people from abstracting a lot of this functionality out in a library for others to more easily build their own stuff with it [1]! If anything the efforts replacing X11 will make it easier to mix and match components, because it gets rid of the focus on the singular X.org implementation. Not saying multiple implementations of the
Read the rest
same thing is necessarily a good thing mind you, but you can't accuse these efforts of making it more difficult to mix and match. [1]: e.g. https://github.com/swaywm/wlroots does some of this to make it more easy to build a window manager that supports Wayland
In On Abandoning the X Server
> massive fragmentation issues across the graphical part of the Linux ecosystem This is a fair criticism. It is true that we see each of the compositors rolling its own extensions to the protocol. But I believe wayland is trying to standardize a lot of the protocols which should cover common use cases. > each new compositor implementation reinvents the wheel many times This is not true. There are libraries like wlroots[0] which you can build on top of. You don't have to redo the work that is already done in other compositors. > application that needs to grab the entire screen will need separate code for each compositor it supports screenshots There is the PipeWire[1] effort to support screenshot and screen capture on wayland in a unified way. > Wayland is also, with its forced composition, hostile to interactive applications requiring low
Read the rest
latency, e.g. video games. Also not true. On a properly implemented compositor, video games frames shouldn't have longer latency to screen than on Xorg. X server has to do composition too, whether you run a compositor or not. [0]: https://github.com/swaywm/wlroots [1]: https://en.wikipedia.org/wiki/PipeWire
In The X.Org Server Is Abandonware?
I agree in general that too many things pop up because people want change without good reason. But Wayland is a highly needed replacement, not just in my opinion, but according to the X.org developers themselves. See e.g. this [1] talk by someone who has worked on both X.org and Wayland. > Why would users ever not stick with something that is stable and just works? As a user, I switched to Wayland 1.5 years ago for two reasons. The first is that Wayland has way better performance than X. It solves some long-standing and highly irritating issues with e.g. screen-tearing that I and others have been experiencing with X. The second is security. Wayland is nearly a prerequisite for proper sandboxing of GUI apps, as X apps can all keylog each other, screen-record each other, inject keys into each other, and so on, without much restrictions. Sin
Read the rest
ce Wayland is backwards-compatible with X via XWayland, which these days has quite good performance, I haven't yet run into an X-only app that didn't just work. As for the issues with nVidia, that's mostly due to nVidia implementing their own Wayland backend (EGLStreams) that is different from what every other graphics card driver uses (GBM), resulting in every desktop environment (GNOME, KDE, etc.) having to implement nVidia support separately from generic Wayland support. The single biggest factor holding Wayland back at the moment is nVidia; my experience is that currently Wayland already works way better than X.org if you have an Intel or AMD card, but is highly broken on nVidia. The second factor holding it back would be that the number of window managers (compositors) for Wayland is lower than for X, currently the main ones are GNOME, KDE, and Sway. But this is changing fast: when I first switched only GNOME worked well; now both KDE and Sway are stable and fully usable on Wayland; and thanks to wlroots, a lot of new window managers for Wayland have popped up [2] and should mature over time. [1]: https://www.youtube.com/watch?v=RIctzAQOe44 [2]: https://github.com/swaywm/wlroots/wiki/Projects-which-use-wl...
In Some Ugly Code Can Get Nvidia's Linux Driver Working with Accelerated XWayland
I have an X1 Carbon 7th gen with a 4k screen (3840x2160). I run it at 2x scaling on Wayland (sway) and I haven't had any issues with native Wayland apps. X apps are rendered at 1x and upscaled, making them blocky or blurry. Apparently there are some apps like Spotify that ignore scaling settings and always render at 1x, but I haven't run into them. There is a fix in progress for XWayland scaling: https://github.com/swaywm/wlroots/pull/2064
In New Lenovo ThinkPad Range with Ryzen 4000 and 4000 Pro Mobile
Take a look at wlroots [0] for a library that massively simplifies the task of writing a wayland compositor. It also gives many of those lower level things "for free". For an even higher-level API built on top of wlroots, you can look at wltrunk [1]. There are standard APIs for screenshots and screencapture, implemented through the desktop portal and pipewire. Check the top-level post for more info about this -- it's part of why Wayland support for OBS has progressed. [0] https://github.com/swaywm/wlroots [1] https://git.sr.ht/~bl4ckb0ne/wltrunk
In OBS Studio: Open-source software for video recording and live streaming

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.