E-Mails are also excellent, if you want to push through something unpopular. Send a long e-mail that will be ignored by most people. Repeat at least once. Then you can reference back to it at a later date.
Sure, that’s the theory. In practice code review often looks like this:
a quick glance to see if the code plausibly does what it claims for longer patches
A long argument about some stylistic choice for short patches
In other words – people were barely reading merge requests before. Code reviews have limited effects as well. You won’t catch all bugs or see if it actually works just by looking at the code. Code reviews mainly serve to spread knowledge about the code among the team. The more code exists in a project, the harder it is to understand. You don’t want huge areas of code, that only one person has ever seen.
Project managers don’t necessarily talk to angry customers directly. They might also choose to chase more features instead of allocating resources to fixing bugs. It depends on what the bosses prioritize. If they want AI and lots of new features, that‘s what they will get. Fixing bugs, improved stability, better performance, etc. are rarely the priority.
Niri implements a scrolling windowmanager like PaperWM instead of tiling like Hyprland. Tiling resizes your windows constantly, while scrolling only resizes when you want it to. If you keep opening windows, Niri opens them to the right of the last one on an infinitely wide workspace. Workspaces are organized vertically downwards. There’s no fixed number of workspaces, they grow on demand. There’s also a zoomed out overview showing you all workspaces and windows. Niri and Hyprland have some similarities though otherwise like lots of keyboard commands to move, resize, arrange windows.
Niri is friendlier overall I would say. It’s worth trying both since they are distinct.
Omarchy is the most complete package for Hyprland, I have seen so far. Installs in under 10 minutes and comes with everything you need installed, nicely configured, and good documentation.
Most window managers come with no GUI apps. They don’t even have a launcher (start menu), status bar, notification area, wifi menu, task bar, dock, etc.
For most window managers you pick and choose a shell, launcher, etc, to combine it with. Then you configure all those separate tools and the window manager to your liking
There are preconfigured packages, distros, and scripts that make sensible choices for this already. Even they usually don’t bring a lot of applications with them.
Omarchy brings a lot of applications in their default install. Check out this uninstall script to get an idea. KDEnlive is a KDE application, gnome-calculator, nautilus, gnome-diskutil, gnome-keyring are GNOME. Chromium is GTK too, I actually don’t know if LibreOffice is. So not many I would dare say. Others ship less.
Dank Linux, a full features shell for Niri, Wayland, mangowc describes it pretty well.
Batteries Included
The age of assembling your desktop from dozens of separate tools and spending hours trying to make it feel cohesive is over. While traditional Wayland setups require you to hunt down, configure, and maintain a sprawling collection of utilities, Dank Linux delivers everything in one cohesive package with minimal dependencies.
The Traditional Way: Package Hunting Simulator
A typical Hyprland, niri, Sway, MangoWC, dwl, labwc, Miracle WM, or generic Wayland setup forces you to learn about and configure a dozen or more separate tools, such as:
Status Bar: waybar, eww, or custom scripts
Notifications: mako, swaync, or dunst
App Launcher: rofi, wofi, fuzzel, or tofi
Screen Locking: swaylock, hyprlock, or gtklock
Idle Management: swayidle, hypridle
System Tools: htop, btop, nm-applet, blueman, pavucontrol
Audio Control: pavucontrol, pamixer scripts
Brightness Control: brightnessctl with custom bindings
Clipboard Manager: clipman, cliphist, or wl-clipboard scripts
Wallpaper Management: swaybg, swww, hyprpaper, or wpaperd
Theming: manually configuring gtk, qt, various apps, bars, compositor gaps and colors
Power Management: custom scripts or additional daemons
Greeter: gdm, sddm, lightdm, greetd
Each tool has its own configuration format, its own quirks, and its own dependencies. You'll spend hours writing glue scripts, debugging integration issues, and discovering missing functionality at the worst possible moments.
I used Niri with KDE apps for a month recently and liked it a lot. Niri is easiest to install already configured as a useable desktop using Dank Linux or Noctalia.
Yes, for window managers, it’s worth finding a good strongly opinionated distro or script to start with, so you don’t have to hunt down and configure a dozen tools.
I like tiling window managers, because I run out of screen real estate and actually close windows. On a regular window manger, I will open dozens of windows and keep them open for many sessions.
Buying a vape pays for itself because it’s so much more efficient. Smoking burns up half of the stuff you want in your bloodstream.
Buy a vape on credit today. Get a medium quality one, it’s good enough if you’re not a serious daily user.