I’ll be honest, if I have to open a console and go edit a few files to configure sway, I’m out. It always starts with “just edit this one file” and balloons to “yeah, if you want everything to work you’ll need this over here, and that over there too, oh and I forgot to document this totally optional but mandatory thing that you’ll find out about on stackoverflow”. Have enough PTSD from “just make && sudo make install” to believe that things are that easy - especially if Arch mentions it.
Thanks for the link, it might come in handy someday, but Wayland is off-limits until my X11 system becomes unstable.
That’s a perfectly fair criticism as far as the average user is concerned, which is why Plasma and GNOME have both made using Wayland as simple as flipping a switch. You at least seemed to imply that you’re a NixOS user, though. Does that not consist mostly of editing config files?
I’ve got great news for you
I’ll be honest, if I have to open a console and go edit a few files to configure sway, I’m out. It always starts with “just edit this one file” and balloons to “yeah, if you want everything to work you’ll need this over here, and that over there too, oh and I forgot to document this totally optional but mandatory thing that you’ll find out about on stackoverflow”. Have enough PTSD from “just
make && sudo make install” to believe that things are that easy - especially if Arch mentions it.Thanks for the link, it might come in handy someday, but Wayland is off-limits until my X11 system becomes unstable.
That’s a perfectly fair criticism as far as the average user is concerned, which is why Plasma and GNOME have both made using Wayland as simple as flipping a switch. You at least seemed to imply that you’re a NixOS user, though. Does that not consist mostly of editing config files?