$ mkdir nix
$ cat > nix/__main__.py << EOL
def main():
# TODO: do what https://nixos.org/nix/install bash script does !!!
print "Nix installed! We love you!"
if __name__ == '__main__':
main()
EOL
$ wget http://url/to/nix.atr.gz
$ mv nix.tar.gz nix/
$ cd nix && zip -r ../nix.zip * && cd ..
$ echo '#!/usr/bin/env python' | cat - nix.zip > nix-installer
$ chmod +x nix-installer
$ ./nix-installer
Nix installed! We love you!
nixpks/lib is amazing resource to some helper functions in Nix, but you have to read the comments in the source code
we need to have tutorials who teach
(alongside existing manual)
“Well it’s a wiki, fix it yourself!”
Have you ever taken a class with multiple teachers at once?
Better to have no documentation then wrong documentation
Keeping your documentation in a wiki also makes it hard or impossible to keep it where it belongs: in version control right alongside your code.
Have you ever taken a class where there’s one jackass in the room who keeps constantly raising his hand and offering his own (often incorrect) opinions?