The technical merits of Wayland are mostly irrelevant - eviltoast
    • onlinepersona@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      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.

      • silt!@programming.dev
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        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?

        • onlinepersona@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          That is true. I have nixos and multiple debian variants running in my house. Nix has a semi-functional graphical interface for modifying that file, but I don’t want to start editing my .profile in order to get sway to work. My current focus is on a different project right now (and will be for the foreseeable future). Experimenting with wayland isn’t on my TODO list right now, especially with the notice in the nixos manual and wiki.