wlroots
tinywm
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wlroots
-
Xorg being removed. What does this mean?
>barrier has been unmaintained for a long time.
As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 5 to debian 12. You can't get a waynergy or inputleap to compile on an OS more than 2 years old. And even then, as you say, it's crapshoot if the particular wayland will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378
- Does Wayland use less battery than x11 in Fedora Linux?
-
Arch Linux odd question
It looks like they actually patched it to filter those modes out, so presumably it worked out of the box and was considered undesirable: https://github.com/swaywm/wlroots/issues/3038
-
Asahi Linux To Users: Please Stop Using X.Org
I haven't experienced any of those. The video game performance hit may be due to vsync, but I don't play games so I haven't noticed.
-
If I install a distro without a GUI, can I still launch graphical applications (like a Firefox window, for example)?
You can however use tinywl. It is an example Wayland compositor that can't do more than displaying one application.
-
Nearest-neighbor scaling on XWayland apps?
Sway/wlroots has implemented this, but I can't find any discussion for KDE.
-
Wofi is SO superior to Rofi
wlroots is archived on github. Is it abandoned? Just saying, that only means they moved git hosts :-D
- wayland-protocols update to allow tearing
-
Wayland harder for DE developers?
A lot of compositors are based no the wlroots lirbary. So they are still sharing the development effort and have a common base, its just in the form of a library rather than a display server.
-
What does gamescope output to?
gamescope use wlroots
tinywm
-
Fedora Workstation 41 to No Longer Install Gnome X.org Session by Default
> Nobody's requiring Wayland.
Yet. Defaulting to it is one step on the path towards removing support for X and independent window managers forever.
I deeply, deeply care about running an independent window manager. A minimal X window manager is a page of code: https://github.com/mackstann/tinywm/blob/master/tinywm.c (yes, plus xlib); a minimal Wayland compositor is tens of thousands of lines of code.
> contrary to your statements, it's perfectly ready for prime time
These comments are full of folks mentioning issues. Wayland does not support my window manager; thus it is demonstrably not ready for prime time for me.
> Wayland is the way forward
It may actually be. I’m not as opposed to Wayland as I may sound! But do you understand how you and other Wayland advocates sound — like advocates? ‘Wayland is the way forward’; ‘there's no future for Xorg’; these things are arguably true, but they are also rather cruel to say (a bit like ‘inevitably you and everyone will die’: it really is true, but it’s also not at all a nice thing to say).
I do think that Wayland or something very like it may be the way forward, but it needs to be an evolution, not a revolution. I know that the party line is that that’s not possible, but I suspect that rather than not possible it is just very hard. It’s always easier to greenfield, and it is always hell to be 100% backwards compatible.
But that’s what it needs to be.
-
RubyWM – an X11 window manager in pure Ruby
Hah. I didn't think this was quite HN worthy at this point - the code is still a mess, and has plenty of bugs. It was however the wm I actually use since I got frustrated with bspwm and did a very minimalist rewrite of TinyWM [1] in Ruby [2] and expanded it from there. It was painful the first few days until I'd had time to add multiple desktops and the start of a tiling mode. But at this point, it's "almost" pleasant for me.
The warnings are real, though, apart from the initial hyperbole - this is likely to break for you in all kinds of horrible ways still. I use very few applications beyond (my own) terminal, (my own) polybar replacement, (my own) file manager, and a browser, and so once Chrome and my own apps mostly started working ok I've had very little incentive to make sure it behaves nicely with anything else and I know the distinction between different EWMH window types is incomplete and broken - just not in ways that usually affect my own use.
[1] https://github.com/mackstann/tinywm/blob/master/tinywm.c
[2] https://gist.github.com/vidarh/1cdbfcdf3cfd8d25a247243963e55...
- What’s something simple but interesting I can build with c
-
WM like i3wm
picking a random bare bones wm tinywm
- TinyWM – A tiny window manager in around 50 lines of C
-
I cannot find the desktop environment for me
Or Check out TinyWM. Its just a few lines of code.
-
WM/DE iceberg
TinyWM
What are some alternatives?
wlroots-eglstreams - A modular Wayland compositor library with EGLStreams support
chadwm - Making dwm as beautiful as possible!
nvidia-patch - This patch removes restriction on maximum number of simultaneous NVENC video encoding sessions imposed by Nvidia to consumer-grade GPUs.
dwm-xcb - A port of dwm to XCB.
leftwm - A tiling window manager for Adventurers
sowm - An itsy bitsy floating window manager (220~ sloc!).
sway - i3-compatible Wayland compositor
hello-wayland - A hello world Wayland client (mirror)
wayfire - A modular and extensible wayland compositor
wayland-rs - Rust implementation of the wayland protocol (client and server).
x11docker - Run GUI applications and desktops in docker and podman containers. Focus on security.
no-wm - Use X11 without a window manager