• RenardDesMers@lemmy.ml
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago

    Probably not the goal of the author but I guess this article convinced me that nix/nixOS is not for me.

    • Atemu@lemmy.mlOP
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 year ago

      This is a lot to take in; it’s basically an overview of all the interesting features of Nix. When starting out, you don’t need this kind of in-depth knowledge. I personally gathered most of what was covered here in over 6-12months of using it and I did just fine.

      It might still not be for you but don’t take this as the reference point.

    • tuto@lemmy.world
      link
      fedilink
      brezhoneg
      arrow-up
      2
      ·
      1 year ago

      Yeah, it really isn’t for everyone. The advantagees it provides is mostly for developers and companies. If you’re a company, managing a NixOS fork is useful, so all users of the system are on the same page always.

      Otherwise the package manager itself can be used on its own. It’s neat being able to use packages from basically any distro without even needing to use a VM.

      Nix is daunting indeed, but cool for those who want such tooling

  • Mactan@lemmy.ml
    link
    fedilink
    arrow-up
    11
    ·
    1 year ago

    nix is like the i3 of package managers. does it work sure but you’ll spend your 80% of your time learning code and configuration to make your sick packaging rice /sarcasm

  • toastal@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I dunno, I don’t trust a guides still recommending flake-utils. You can make the same four loop in like 4 lines of Nix which is a smaller diff & doesn’t pollute your downstream consumers with a useless dependency. Flakes also don’t eliminate pointless builds, fileset or filtering the src can & the only tool with file tracking on by default is the Git VCS specifically (which also involves the intent to add flags which is the other side of annoying).