News for hackers. Stuff that matters.
Re:Typing Nix by sly010 on Friday June 23, 2017 @11:02AM (#14619659)
Sure it would be nice to have types for refactoring, but a more useful set of features would be:

- baked in fetchurl, fetchgit for easier bootstrapping

- a functional dsl for rendering filesystem hierarchies - instead of the find/sed/awk galore. 50% of the time when my nix recipe breaks it's not a nix syntax issue but something with bash. (reading nix is an exercise in learning new unix features)

- drop the channel feature entirely and make releases immutable tar files with hashes. I use nix as a build system on macos and right now a nix-channel update is a sure way to break all my builds which is the opposite of nix's promise

EDIT: formatting

Re:Typing Nix by regnat on Friday June 23, 2017 @11:07AM (#14619692)
For your last point, you don't have to use the channels (which will anyway be deprecated at some point iirc), and you can pin the nixpkgs version in your nix files (like it is done in https://garbas.si/2015/reproducible-development-environments...)
Re:Typing Nix by bennofs on Friday June 23, 2017 @12:34PM (#14620442)
for your first point., what about `builtins.fetchTarball` and `builtins.fetchurl` (`fetchgit` is in nix unstable afaik)