So we can clearly see the most popular distros and the reasons why people use them, please follow this format:

  • Write the name of the Linux distro as a first-level comment.
  • Reply to that comment with each reason you like the distro as a separate answer.

For example:

  • Distro (first-level comment)
    • Reason (one answer)
    • Other reason (a different answer)

Please avoid duplicating options. This will help us better understand the most popular distros and the reasons why people use them.

    • sntx@lemm.ee
      3·
      1 year ago

      Single command to compile & install packages from many git repos

    • sntx@lemm.ee
      2·
      1 year ago

      A great selection and amount of packages and modules to build/install/enable

    • sntx@lemm.ee
      2·
      1 year ago

      A cool logo, meaningful rolling release version names and stickers

    • sntx@lemm.ee
      2·
      1 year ago

      You get it for the low price of loosing all fun/motivation in setting up, customizing and mintaining machines with other distros

    • loggy@infosec.pub
      1·
      1 year ago

      I have been thinking to give NixOS a spin but feel like it’s above my brain capacity for me to handle. Do you also use homemanager and Flakes? Homemanager kinda makes sense (manage packages for non root users) but what does Flakes do?

      • fabian_drinks_milk@lemmy.fmhy.ml
        31·
        1 year ago

        I am already trying it and I am still no expert. How I understand flakes is that it is a file with inputs, like nixpkgs and other flakes or repos you might depend on and some outputs that can be things like a nixshell with packages and environment variables, custom packages and configs like your NixOS configurations and home manager. When you use your flake for the first time, by entering a nix shell with nix develop, building a package with nix build, rebuild your NixOS system with nixos-rebuild --flake .#<hostname>, etc, nix will generate a flake.lock file that stores the hashes of all of your inputs and thus pinning the input versions. This means that if you ever run any of those commands again, you should get the same result because the inputs are pinned and the same version. If you want to update, you just run nix flake update and it will regenerate the flake.lock file with new hashes for the newest version. The advantage with flakes is that it is fully reproducible, even if one of your dependencies changes, because the hash is specified and centrally managed in the inputs of your flake.

        Nix flakes can be used for your NixOS system by adding the nixos configurations in the outputs of your nix flake and adding the dependencies like nixpkgs to the inputs. You can also combine it with home manager by either specifying it as a separate output or adding it as a nixos module inside the nixos configurations output. You just copy your existing nixos and home manager config to the folder with your flake and reference them inside the flake.nix. If you added home manager as a nixos module, you only need to run nixos-rebuild switch --flake <path-to-flake>.#<hostname> and it will automatically rebuild both your NixOS configuration and home manager configuration. You can then backup the folder with your flake and configurations by uploading them to GitHub for example.

        The best resource I found was this 3 hour video by Matthias Benaets: https://youtube.com/watch?v=AGVXJ-TIv3Y&feature=share7

        • loggy@infosec.pub
          2·
          1 year ago

          Thanks a lot for the detailed answer. It does sound complicated haha. I should probably follow along the YT video. Thanks again!

    • sntx@lemm.ee
      1·
      1 year ago

      Do it once, do it right. Save work be redeploying the same configuration (or submodules) on mutiple machines or the same machine multiple times.