• tom42@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Fun fact: I use NixOS since six years now and at least in the first two years the Arch Wiki helped me a lot to understand the NixOS configuration options.

    • Laser@feddit.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      That’s the main crux with NixOS, it does a lot of stuff in the background for you that in my opinion you should know why it’s being done the way it is. As such I consider Arch a good distro for a beginner who wants to learn the inner workings of Linux, while NixOS is a better-engineered distribution that takes care of the system for you. Arch’s goal is to be simple for the maintainers which means it’s very close to what one might consider a “standard Linux”, and its wiki is mostly a documentation of exactly that.

  • apt_install_coffee@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    NixOS needs what is IMO the killer feature of Arch: the wiki.

    Comprehensive documentation on not only the OS but the additional packages that we use is what drew me to Arch, and the thing that makes me swear in frustration whenever I have to use Ubuntu/Debian.

    NixOS is an excellent OS that has the promise of being every bit as hackable as Arch, but far more stable. Problem is, configuration is very different and needs extensive documentation to reduce that friction point.

    • Atemu@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      NixOS needs what is IMO the killer feature of Arch: the wiki.

      NixOS has a killer feature which obviates a wiki for most such purposes: NixOS options. They document themselves!

      You don’t need to look up a wiki on how to install and enable i.e. paperless and all the other services it depends on, you simply set services.paperless.enable and NixOS configures everything for you internally.

      The option tells you roughly what it does internally and the other options provide pointers for things you might want to tweak about it. The services.paperless.extraConfig option for example tells you how to configure it (pointing to upstream documentation in this case) and even gives an example on what you might want to do.

      Another example is how to install Steam. In Arch, the wiki must tell you all the manual steps required to enable multilib, install the steam package, install 32bit dependencies, yada yada.

      In NixOS, you simply set programs.steam.enable = true;. Off to your games.
      You wanna customise the Steam package to add additional flags, pass env vars or add additional packages your weird Linux-native indie game needs? programs.steam.package tells you how to do that right in the place where you do it.
      While you’re looking for steam, you might also come across hardware.steam-hardware.enable which you need to set in order to make your Valve Index and Steam Controller work properly.
      You wanna start Steam in a gamescope session right from the display-manager? programs.steam.gamescopeSession does it for you. No need to copy paste some snippet that you’ll instantly forget about and maybe breaks in a few months. programs.steam.gamescopeSession is maintained upstream by NixOS, so if it breaks, someone will go and fix that and nobody needs to adjust any of their copy-pasta because they’ll just update as they always do and it just starts working again.

      None of this is perfect yet and the quality of documentation of NixOS options really varies but I think you get the idea here. I already rarely look at the NixOS wiki to configure my system because the system configuration tells me what I need to do already and this will only get better as options get refined.

      the promise of being every bit as hackable as Arch

      I don’t think it makes that promise and I don’t think it’s true.

      NixOS is about doing things “properly”; applying software engineering to software environment management.

      Whipping up a quick hack is much more complicated and time intensive on NixOS than doing so on Arch because it’s way more abstract. You can’t just quickly replace some binary with your own compiled one, you need to use NixOS’ systems to wire in the binary and build it with Nix to begin with.

      Maintaining a system (even one with terrible hacks) is much simpler in NixOS however.

      • hschen@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I installed NixOS on a laptop and tried to run a steam game and it just straight up didn’t launch anything, went to the wiki to figure out the amd drivers, opengl whatever put like 10 new lines in my nix config rebuilt restarted still nothing works, after about 2 hours i just swapped back to arch and the games launched straight away, so for me it wasnt as easy as you may claim it to be. I also tried it on my desktop before and it was a better experience, but still not great. The nix config file is a bit of a mess of options that you have to dig into wiki pages and searching stuff to figure out how to get some stuff to work

      • Helix 🧬@feddit.de
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        NixOS options. They document themselves!

        Didn’t read past that as you clearly don’t understand what the differences between documentation, a tutorial and code comments are.

        • Atemu@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Do read past that and you might understand why NixOS options are a type of documentation. They’re not “code comments”.

          • Helix 🧬@feddit.de
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            I have tried NixOS, the documentation in many options is subpar. Only the most interesting packages get good documentation. I’ll give NixOS a few more years until I try it again, but currently it’s rather a hobbyist and ‘tinkerer’ distribution. Which is fine, but I don’t want to learn domain specific stuff which is different from all of the rest of Linux.