Remember the days when everyone and their pet iguana was raving about Arch Linux? You couldn't escape the ever-so-subtle "I use Arch BTW" remarks in every Linux forum. Well, move over, Arch, because NixOS is here to steal your thunder! Nowadays, it seems that you can't browse YouTube or read a blog without stumbling upon someone extolling the virtues of NixOS and how it is the epitome of computing perfection. But hey, who needs critical analysis when we can jump on the hype train and declare NixOS as the new Arch? Because that's exactly what's going on. NixOS has now become the self-proclaimed prodigy that's poised to dethrone Arch Linux as the holy grail of Linux distributions. The time is calling, my friends! It's time for you – the seasoned Linux enthusiast – to dust off your keyboard warrior capes and embark on a new crusade. So, grab your Tux plushie (or, your pitchforks if you belong to the world of devils) and let's embark on an adventure through the enigmatic world of NixOS (and let the memes commence)!
  • msage@programming.devEnglish
    21·
    1 year ago

    You can be sure software {…} will behave the same

    never had that issue before, as long as they have the same version and config

    avoid dependency conflicts

    I have those on Gentoo sometimes, possibly because I overloaded USE too much, but that’s not something I have to deal with on Debian/Mint.

    You can time travel back to a previous state

    wasn’t that possible before with snapshotting (btrfs/lvm)?

    If it allowed me to avoid systemd, I would be willing to give it a go. Perhaps I will try it in a VM, but it’s not going on any baremetal for now.

    • jim_stark@programming.devEnglish
      4·
      1 year ago

      You can be sure software {…} will behave the same

      never had that issue before, as long as they have the same version and config

      Pure:

      If you uninstall a software it might still have residues. If you install a faulty driver, even if you uninstall it, it might still permanently mess the system configuration.

      But with nix if you uninstall something it’s like it never existed in your system.

      Reproducible:

      With nix all the apps in your OS are configure using a single or a few config file(s). So if you want to setup another system the same way you don’t have to go hunting for dotfiles.

      avoid dependency conflicts

      that’s not something I have to deal with on Debian/Mint.

      Because you are recommended to use only software present in the repositories. If you are the kind of person who doesn’t need software outside of your OS repositories then of course you might never need to worry about dependencies. Other people are doing the job for you.

      But if you want to software not in the repos and even if you want to package it for your OS you might run into dependency issues. Never with nix. It’s more for people who don’t mind packaging software for themselves (and the community) and don’t want to deal with nasty dependency issues.

    • uthredii@programming.devEnglish
      22·
      1 year ago

      never had that issue before, as long as they have the same version and config

      Then you are very lucky. “It worked on my machine” is a meme for a reason.

      wasn’t that possible before with snapshotting (btrfs/lvm)?

      I haven’t used snapshotting with those before. I guess the difference is that with nix it is done by the package manager by default, with btrfs/lvm you would have to set that up independently (please correct of this is not the case).