> - Examples that just don't work. yes, the nixpkgs changes and some old articles might no longer be accurate :/ > - Commands that run and no output is given,

> - Examples that just don't work. yes, the nixpkgs changes and some old articles might no longer be accurate :/ > - Commands that run and no output is given, even though the text I'm following says it should output information I need. could you give an example? > - Do I need nix-darwin? Well, the readme explains what it is: "Nix modules for darwin, /etc/nixos/configuration.nix for macOS." What? (Finally I found an answer at Stack overflow, and it seems I don't need it. Seems to be kind of NixOS on top of macOS) yes, you don't need it for what you described. nix-darwin is basically to provide configuration functionality of NixOS to your Mac. Nix-darwin is 3rd party product that's written in Nix for Nix. Similarly Home Manager. > - Can't build with nix-build. After long time searching it seems like you're supposed to run nix-build -E 'with import <nixpkgs> {}; callPackage ./default.nix {}' - shouldn't there be a simpler way for this common case? a lot of people wrote about it. This is a convention that evolved from nixpkgs, it's still not officially supported by CLI tool (that's why the command looks so complicated, it's similar to calling `python -c "<whatever>`), seems like the default.nix file which is very similar in concept to setup.py (as you can put whatever you want inside) is being replaced by more stricter flakes.nix file. Which in a way brings some similarities to the callPackage convention. > - An issue open since 2018 that the manuals simple example doesn't build: https://github.com/NixOS/nix/issues/2259 https://github.com/NixOS/nix/issues/2259 People chiming in years later that they only could build the example after reading the suggestions in that issue. Because software evolves and old versions of file like to disappear with time. I run into this as well, although it was nix pills documentation. My solution was to simply get the new version of hello and use that. Although I agree, that's still unnecessarily confusing. I think a proper solution would be to host the file on the own server. Or even better, make a basic hello.c file and list its content in the doc. > - And now I can't start my nix-shell because it says there's a problem with SSL certificates. I'm giving up. You most likely uninstalled nss-cacert package. Perhaps `nix-env --rollback` would help.