Nix at work: FlakeHub Cache and private flakes

  • I appreciate someone from the project commenting here. I left Nix because it just has too many warts, and unfortunately, they've only increased over time, which is the opposite of what I expected.

    - I'd update Nixpkgs, and my build would stop working. The logging was awful, so fixing it took hours.

    - The mono repo sounds nice, but selective updates are almost impossible.

    - Building our Go project in a Nix package was nearly impossible with private GitHub repos, so we moved on.

    - Bash scripts never work because binaries are never where they should be in Linux.

    I could go on, but my experience with Nix and NixOS left me with significant scars. I’m hopeful that someone will eventually create a more user-friendly deterministic OS.

  • Given the extensive infrastructure you and others are building around flakes in the Nix ecosystem, despite flakes still being experimental, what does the roadmap look like for your efforts, and more broadly for officially establishing flakes??

  • Has the situation between you guys and the Nix community cooled down yet?

    I have honestly avoided NixOS for quite a while because the situation seemed "unstable". I don't particularly care for the complaints brought about by the open letter, I do however worry if a distribution/community is imploding.

  • I love the idea of Nix, but the current implementation seems too impossibly complex to ever go mainstream. Dynamic hard-to-debug DSL, loads of novel concepts, difficult to do a piecemeal transition, etc. One poster in this thread reported how their supposedly immutable system configuration broke with an update.

    Is there anything on the horizon which could embrace the ideas in a better package? Does Guix smooth over enough rough edges?

  • Can someone do a ELI5 of Nix and flakes for me? I've looked at the docs numerous times and bounced back each time after I failed to understand the USP of Nix...I just don't know what's the main use case(s).