If your deployment story is still cp sway /usr/local/bin, you've already lost; with Nix it's one derivation that spits out riverd plus whatever WM you fancy. A bit more granularity buys you decoupled policy, smaller attack surface, and maintainable code instead of yet another all-in-one blob.
Cool idea, but for a one-liner deployment I still reach for a monolithic sway build I can throw in /usr/local/bin and move on.
If your deployment story is still
cp sway /usr/local/bin, you've already lost; with Nix it's one derivation that spits out riverd plus whatever WM you fancy. A bit more granularity buys you decoupled policy, smaller attack surface, and maintainable code instead of yet another all-in-one blob.