Hyprland has way more features than Sway. There's 1:1 touch gestures, animations, and per-window screen sharing. Also there's all kinds of tiling configuration available, which allows Hyprland to do manual and/or automatic tiling.

Sway's lack of features is also its advantage, because it's been the most stable and consistent window manager/compositor experience I've ever had on Linux (X and Wayland). Hyprland sometimes has its bugs, which does make sense given how young and fast-moving the project is.

I would have never tried it without having installed Garuda on a couple boxes recently. It was the first time I've seen all the ricing done correctly. I've never been able to fully replicate the configs done by YouTubers or /r/unixporn, something always didn't quite work, usually fonts or the status bars or color themes. Garuda with hyprland is pre-riced and is extremely fast. I could absolutely notice lower latency in the console. I'm definitely going to use it more.

I've used i3 and then sway since a few years, never had any problems (nothing I remember at least).

Then I tried out hyprland, and I had multiple crashes a day, and not really saw any benefit compared to sway. I also needed to disable all of the animations which are enabled by default, because they were nauseating and made everything slower (compared to the snappieness of sway, still faster than macos/windows).

I would have probably invested some time into debugging the issues, if I had seen any reason why I would want to use Hyprland over Sway.

After a few weeks I switched back to sway, and never felt the urge to try it again.

I started with hyprland when I switched my desktop from windows to arch recently (june) and moved to sway. I ran into bugs and behaviour I don't like:

- Having two monitors and turning them off (either physically or through dpms) shifts all workspaces to the last monitor that is on, even if it's on for a split second,

- Turning off monitors (physically/dpms) caused waybar to crash.

I don't have those issues on sway, so I'll stick with it until hyprland matures a little more.

I've given hyprland two tries. The first time it was exceptionally laggy and crashed all the time. The second time (earlier this year) hyprland was performing better, but it still had enormous CPU power draw, lagged with disabled animations, for whatever reason had terrible font anti-aliasing (with the same font-config settings as sway). Maybe a full rewrite to this new stack will help, but I doubt it.

Have not tried Hyprland but on three separate occasions with three different machines I could never get Sway working. One got close but it would constantly crash.