Hyprland 0.44
hyprland.org
hyprland.org
> Hyprland is an independent, highly customizable, dynamic tiling Wayland compositor that doesn't sacrifice on its looks. It provides the latest Wayland features, is highly customizable, has all the eyecandy, the most powerful plugins, easy IPC, much more QoL stuff than other compositors and more...
A Wayland compositor is a fully autonomous Display Server, like Xorg itself.
...
Wayland compositors should not be confused with Xorg window managers.
"movetoroot" is discodant - it deletes information.
It's been remarkably reliable. There are definitely rough edges, but it's been a pleasure to use in general. It even works very smoothly with Microsoft teams, even screensharing works perfectly!
Not planning on moving to anything else anytime soon, wonderful experience and I'm glad to be one of the earlier adopters of a wayland-first system.
its a great tiling window manager
That and I can't get my mouse cursor big enough or colorful enough -- and more of a wayland issue is that the pointer will change depending on window.
I don't really use it to its fullest extent though
I also maintain a very popular tiling window manager now (after years of suffering through breaking configuration changes with other twms) and this is the one thing that I will not budge on as a maintainer: Breaking configuration changes are unacceptable. Period.
From the contribution guidelines on the project README[1]:
> Breaking changes to user-facing interfaces are unacceptable
> ...
> No user should ever find that their configuration file has stopped working after upgrading to a new version of komorebi.
[1]: https://github.com/LGUG2Z/komorebi?tab=readme-ov-file#breaki...
Right now there is support for dynamic configuration through commands executed through a script at startup (like bspwmrc etc), and declarative configuration through a static file which can be hot-reloaded.
Basically all new features and documentation are declarative-first, and there is a command that can generate a declarative configuration file from a running instance configured using a dynamic configuration script.
So if you're new to the project, you probably don't even know that the older configuration method is a thing, and if you come back to the project with a very old dynamic config script after a long time, everything you remember still just works, and you're just a command away from migrating to the format that everyone else is now using.
That being said, there is definitely a whole bunch of code that I would love to get rid of some day :)
Specially the keyboard/trackpad support. It's always been underwhelming with Linux. I know this is a subjective take and it's unrelated to Hyprland.
I hope that my next laptop can finally be the final step off to the Linux laptop, because I would love to use Hyprland.
[1] https://www.reddit.com/r/AsahiLinux/comments/1atrb13/im_reco...
KDE and GNOME both work out-of-box for most features and configurations. If you don't try to chase the r/UnixPorn dream you can end up with usability in spades.
I use custom external keyboards though, so maybe I’m not the best reference for your specific complaints.
Pop OS's built-in tiling manager doesn't have these problems and it has a toggle for alternating between floating and tiled, which is helpful at times. It gets me to where I want MacOS to go without any of the exhaustive setup and just works.
As much as I would like to go with Hyprland for the fancy animations and stuff I don't have the patience for instability or configuration files breaking after updates. I am on team Cosmic for now.
That being said, I am a W^X person so I don't really like some of the (x86_64-specific) aspects of their plugin systems. I need to publish my #ifdef-it-out-with-fire patch at some point...
To this day, Wayland has problems that X never had, particulary screen-sharing or window management being dependent on the compositor implementation. What problems does this solve?
I don't actually see a landing page anywhere that explains what Hyprland is :)
It says "Tiling Compositor" as its first words. That's what it is.
It's not a "window manager" since that's an X11 term, and this is a Wayland Compositor, not an X11 Window Manager.
I feel like the landing page explains very clearly what it is for the target audience, which is someone who uses wayland and knows what a tiling compositor is.
Just stick to the web version, it's way more stable